-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak #211
Comments
I already created issue about this on node-socks-proxy. |
And looks like there is issue in http-proxy-agent and https-proxy-agent . I'm trying to find it, but now we are on workarounds :D . I spend hours on this issue and looks like this problem not in uashield. |
Forgot to add some logs. First, there's noticeable the worker count degradation with some errors. But when the thread count reaches 16, there're a lot more of the same errors thrown. The log of errors is very long. This short snippet was captured at the moment the memory usage went up.
|
Program settings
Version: 0.0.31 (latest)
Command line:
./uashield --no-sandbox
(doesn't start without--no-sandbox
parameter)Proxy: enabled
Max threads (just my preference): 128
The amount of threads doesn't matter because the same happens with 256 or even 32 threads.
Environment
Oracle VM VirtualBox (virtual machine)
OS (
uname -a
output):Linux kali 5.16.0-kali6-amd64 #1 SMP PREEMPT Debian 5.16.14-1kali2 (2022-03-23) x86_64 GNU/Linux
RAM: 3 GB
Behavior
When the program is running normally, the CPU utilization is about 20%, and the RAM usage is 1.5/3.0 GB.
After running for quite a bit, the program starts gradually eating all the memory available, and the CPU load rises to 100% immediately.
Memory usage per process right before the crash:
By the way, the program window doesn't respond anymore, and the terminal output is scrolling way faster than normal. Among the usual logs, there's
superagent: double callback bug
message appearing every few seconds.Then the program runs out of memory, and the crash happens. Here's a message you can see in the terminal:
Tried to gather everything I noticed. Don't really sure what else I can provide, so here it is.
The text was updated successfully, but these errors were encountered: