mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 08:05:52 +03:00
[GH-ISSUE #1938] Memory leaks when working for long time #1929
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1929
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nisimjoseph on GitHub (Feb 15, 2024).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1938
Originally assigned to: @NghiaTranUIT on GitHub.
Description
First thing, thank you for a great product!
we have developers working with this product for days, literary days for the ProxyMan is running. while running it loads memory and get to high amount of GB of memory that stuck the Mac.
Steps to Reproduce
Current Behavior
memory get too high and stuck the mac
Expected Behavior
if the ProxyMan get to a limit of rows, it need to dump the previous ones.
for example, I will have default of 5000 lines and after those the 5001 and older will be deleted so the memory will be keep on reasonable range.
the UI Preferences need to have the limit set or Unlimited for those who needs it.
Environment
@BjornRuud commented on GitHub (Feb 21, 2024):
I experienced this too on 4.16.0. I have "Auto Clean Up Resources If Memory Usage Is High" turned on in settings, but over a number of days the Proxyman process used up all the memory.
@NghiaTranUIT commented on GitHub (Mar 2, 2024):
@BjornRuud it's expected because Proxyman accumulates a lot of traffic for a number of days. You might Click on the
Clear Sessionbutton to release unnecessary data.@nisimjoseph commented on GitHub (Mar 2, 2024):
@NghiaTranUIT yes, but when you leave it off for a day because you didn't remember to turn it off, it gets to 20–40GB of memory usage.
That doesn't make sense to me.
I think you need to limit the data to 6 hours of accumulation and remove the rest.
you can have a setting to make it accumulate forever, but it is supposed to be turned off by default.
@NghiaTranUIT commented on GitHub (Mar 2, 2024):
@nisimjoseph it depends on how many SSL items are in the Tool menu -> SSL Proxying List. By default, If there are no SSL Entries, Proxyman only proxies the data without holding the body.
If it has some wildcard (e.g.
*) or Google Chrome in the SSL Proxying List, Proxyman will decrypt all HTTPS traffic and hold it in memory. So it might consume more RAM.Can you double check and remove all SSL Entries and test it again for a day?
@nisimjoseph commented on GitHub (Mar 2, 2024):
@NghiaTranUIT I agree with this, but the Proxy domains are set only to the needed domains. and while developing, we have lots of network calls on our domains. I saw one computer totally stuck because of the 40GB memory the ProxyMan took only by handling our proxy traffic.
It occurred to many Frontend developers, including me, because I forgot it open for 10 hours, got to 15GB memory.
@NghiaTranUIT commented on GitHub (Mar 2, 2024):
May I ask what Proxyman version you're using? From the v4.11.0 (released on Sep 13, 2023), I fixed a memory issue when each request has unnecessary 4 primitive locks => Causing huge memory usage.
@nisimjoseph commented on GitHub (Mar 2, 2024):
yes, I work with the latest, and I saw the issue in 4.16v as well.
I use 5v, and tomorrow I will turn it on all day to check the memory usage for 8 hours.
@NghiaTranUIT commented on GitHub (Jul 23, 2024):
Fixed with the latest build v5.6.1 👍
@raxityo commented on GitHub (Jul 26, 2024):
Hey @NghiaTranUIT,
I am on the latest version:
I just updated to this version a couple of days ago, but still experiencing high memory usage eventually leading to the network and Proxyman being unresponsive in the background.
Screenshot showing system prompt to quit an app due to reaching memory limit:
Unfortunately, I quit the app already. But if there are any dump or logs that I should be grabbing before quitting, feel free to let me know. I can do that if it happens again.
@lwj1994 commented on GitHub (Oct 28, 2024):
@NghiaTranUIT this bug is still alive on Version 5.9.0
Proxyman Version 5.9.0 (50900) | macOS: Version 14.5 (Build 23F79)
@NghiaTranUIT commented on GitHub (Oct 28, 2024):
@lwj1994 can you follow this https://github.com/ProxymanApp/Proxyman/issues/1938#issuecomment-1974747219
to remove some items in the SSL Proxying List. It will fix your memory issue.
From what I did, the latest build has fixed the big memory leaks issues, but not 100%.