Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

RAM usage stays high after Clear All

Open
  • Is something wrong?
#122 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@NghiaTranUIT is already working on this.

Since Oct 2, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop, networking, performance

Research direction

Reproduce the issue by capturing about 2 GB of traffic and using the toolbar's Clear All action. Trace the Clear All handler and captured-data lifecycle, then verify that the captured data is released and RAM returns near normal after clearing.

Written by the indexing model from the issue text.

Description

DONE
  • Problem: After capturing about 2 GB of traffic and clicking Clear All in the toolbar, RAM usage stays around 2 GB.
  • Expected: Clear All should free the captured data and bring RAM usage back near normal.
Dominant language
Swift
Stars
444
Forks
21
Avg merge
53m
Merged PRs (30d)
12

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProxymanApp/TCPViewer

All issues in ProxymanApp/TCPViewer

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.