Open mark007 opened 10 years ago
This seems to happen when devices are set incorrectly to use "client" mode rather than "server" mode. Do you think it would be much of a code change to stop vSPC.py memory usage increasing in cases where vms are set to the wrong mode?
We had an issue with the original vSPC.py process dying every few minutes, with lots of connections. With this newer vSPC.py it doesn't die every few minutes, it lasts for a number of hours but eventually dies.
I can see in dmesg in my centos machine out of memory error relating to vSPC, and can see in top output, the %MEM is constantly growing over a number of hours, even though the number of vSPC.py connections (68) remains constant. Is there a memory leak that could cause this, where can I check to see whats causing memory to increase indefinitely until the process is killed?