ProxymanApp
Out of control memory usage
Description
System regularly asks me to force quit as I'm out of memory with Proxyman using many gigs of memory. Also beach balling and unresponsive. This is an issue that seems to have been introduced about 3 months ago. All my colleagues are also getting the issue. And no it isn't because we are ssl enabling all chrome requests, etc as stated here: https://docs.proxyman.io/troubleshooting/proxyman-consumes-too-much-ram-and-unresponsive
Steps to Reproduce
- run proxyman all day
- check memory usage
Current Behavior
Memory usage is out of control causing system instability and memory warnings
Expected Behavior
Behave like a normal app
Environment
- App version: e.g Proxyman Version 4.8.2 (48020)
- macOS version: e.g macOS 13.4.1
@philosopherdog just wondering: Do you use * wildcard or Google Chrome on the SSL Proxying List?
and how many requests that you have when it hits the memory warning?
Ok I'm investigating this. I have a wildcard for slack in my block list to hide but don't block. However in my ssl list I have a wild card for the business business.slack.com and it's picking up all of the slack communication! I also have in my ssl list to block slack but I guess it's ignoring all of the blocks and grabbing all the slack traffic. It's a pretty quiet morning and already I proxyman is over 2gb of memory! The lists for ssl and blocking are confusing as to what is taking precedent.
The app starts with 92 mbs. Within minutes it's jumping to double and then it just shoots up from there. This is ridiculous.
Ok something is now working better for the first time in 3 months! I think it's very hard to understand what all these filters are doing. Filters that are supposed to hide don't seem to. I guess the key is turning on ssl using a wildcard for a whole bunch of frequent requests seems to be the underlying cause.
When you add business.slack.com to the SSL Proxying List -> It will decrypt all data and store it in memory. You should remove it from the SSL Proxying List.
I will revisit how the Block List + Hide works, to make sure it doesn't automatically add to the SSL Proxying List. Thus, it can fix the bug 👍
@philosopherdog I admit that it's a bug from Block List. It should not automatically add this domain into the SSL Proxying when we create a Block List Entry. So, Proxyman never captures its decrypted data -> Increases memory usage.
I'm going to fix it and send you a Beta build 👍
@philosopherdog you can try this beta build: https://download.proxyman.io/beta/Proxyman_4.8.2_Fix_memory_issue_on_Block_List.dmg
You should remove all current SSL Proxying Lists, it will fix your issue 👍
Changelog
- When creating a new Block List -> It doesn't add it to the SSL Proxying List -> No decrypt HTTPS data -> No memory issue
This has been a long standing issue hasn't it? I have noticed it for several months at least. When is this fix being released to prod? I am on setapp so the beta won't help. I am able to work around this for now by not expecting block ssl to take precedence and setting up my lists accordingly. Is the other block/hide filter also not working. Pretty sure I see requests in PM that are supposed to be hidden.
@philosopherdog yes, it's a long issue but now it's fixed.
Is the other block/hide filter also not working
From what I know, it's still working fine.
I will release the new build today 👍
@philosopherdog maybe it's a different Memory Issue. I confirmed that the Block List issue is fixed.
Can you share with me how many items are in the Tool menu -> SSL Proxying List ? Does it have Web Browsers or Wildcard, which can match a lot of requests?
same here, proxyman is the only app constantly causing my mac to run out of memory, I do run it all the time though, but still, memory keeps going up and up and it doesn't seem to be able to clean things up, I only have like 10 entries in the ssl proxying list, without many wildcards
clicking the trashcan icon does work, so there's something there that maybe should be run as part of the auto cleanup
May I ask: @aexvir what Proxyman version you're using? and how long do you open the app? You can see the latest ID Number and share with me.
everyone on my team suffers from proxyman tanking the macs memory. we all remember the old days when this app just worked. if i forget to clear memory i end up having to reboot. frustrating.
Sorry for this inconvenience. @philosopherdog not sure what Proxyman version you're using? Try to use the latest build because we discovered a Leaked memory (due to a lot of unused NSLock) on v4.11.0
May I ask: @aexvir what Proxyman version you're using? and how long do you open the app? You can see the latest ID Number and share with me.
I was using 4.14.0 (49500); just updated to 4.15.0