ProxymanApp
Network traffic hangs and timeouts when proxyman left running after Mac resumes from sleep
Description
Network traffic hangs and timeouts when Proxyman is left running after Mac resumes from sleep. This has been happening for as long as I've had Proxyman on many different versions of Proxyman and macOS versions.
Essentially if I leave the application running for a long period of time, usually overnight and wake the computer from sleep while Proxyman application is still open the network traffic stops working. Web browsers show error screens to check firewall/VPN, and other applications just timeout.
Proxytman UI shows no traffic at all, in-fact all the historic traffic disappears from the UI!
It's quite easy to fix, closing and re-opening Proxyman always fixes the issue, but of course, I've lost any historical traffic I had previously captured.
Steps to Reproduce
- Leave Proxyman running all day and overnight while MacBook sleeps
- Wake MacBook from sleep in the morning
- Observe Proxyman is still running but network traffic times out
Current Behavior
Proxtman stops collecting and processing traffic, computer network requests timeout.
Expected Behavior
Proxyman should work when resuming from long periods of sleep and use, alternatively, the application should stop overriding the macOS proxy when the Mac goes to sleep and resume after.
Environment
- Proxyman 4.9.0
- macOS 14.0 Beta (23A5301g)
I've also observed the same issues on Proxyman versions dating back to 1.0 and macOS versions including Ventura so I don't believe this is caused by environmental compatibility.
Proxyman should work when resuming from long periods of sleep and use, alternatively, the application should stop overriding the macOS proxy when the Mac goes to sleep and resume after.
Thanks. It seems feasible to do it. I will try to reproduce it in my send and fix it 👍
Any update on the bug, I met the same issue on proxyman 4.9.0 on mac on macOS 13.6
@JoshuaZhu86 let's use the latest version 4.15.0 👍 We've fixed the memory issue due to unused NSLocks from v4.11.0
@JoshuaZhu86 let's use the latest version 4.15.0 👍 We've fixed the memory issue due to unused NSLocks from v4.11.0 seems working now, great work !