All Forums
> NetWorx
> Current topic
Possible memory leak
Started by xrmb
Possible memory leak 08 October 2016, 10:17 |
Registered: 7 years ago Posts: 8 |
OS: win 2012 R2
It was running for a week, last night it was at normal memory usage. I don't think anything special happened in the last 24hrs. I have seen it before, but installed an update since, hoping it was fixed. Guess not.
Let me know if there is anything I can do to help debug, like a memory dump or something.
Re: Possible memory leak 08 October 2016, 10:45 |
Admin Registered: 18 years ago Posts: 3 519 |
Re: Possible memory leak 09 October 2016, 01:00 |
Registered: 7 years ago Posts: 8 |
Re: Possible memory leak 09 October 2016, 13:25 |
Admin Registered: 18 years ago Posts: 3 519 |
It could be an app that opened a lot of sockets, but not closed them for a long time.
Try going to the Hidden Settings and set Keep track of TCP/UDP connections to False.
Try going to the Hidden Settings and set Keep track of TCP/UDP connections to False.
Re: Possible memory leak 09 October 2016, 23:27 |
Registered: 7 years ago Posts: 8 |
Re: Possible memory leak 16 October 2016, 22:05 |
Registered: 7 years ago Posts: 8 |
Re: Possible memory leak 17 October 2016, 07:35 |
Registered: 7 years ago Posts: 8 |
Ok, I have a full and "full minidump", each one is 750mb (500mb compressed). Let me know if it is of any potential use.
I also noticed this: when I logged in the computer Networx was at 2.5gb memory, I closed my torrent client and the memory usage dropped to 750mb. Not sure if it is related, but it sure looks like it. But the torrent client is open 24/7, and so is Networx. According to its own logging the torrent client does around 400k connections per day, but I have not seen any memory increase for Networx in the last 10hrs. Of course there are a few other programs that use the internet running.
I also noticed this: when I logged in the computer Networx was at 2.5gb memory, I closed my torrent client and the memory usage dropped to 750mb. Not sure if it is related, but it sure looks like it. But the torrent client is open 24/7, and so is Networx. According to its own logging the torrent client does around 400k connections per day, but I have not seen any memory increase for Networx in the last 10hrs. Of course there are a few other programs that use the internet running.
Re: Possible memory leak 17 October 2016, 11:03 |
Admin Registered: 18 years ago Posts: 3 519 |
It's probably not so useful as NetWorx doesn't come with debug information and we won't be able to determine what has consumed the memory.
I'd suggest to turn off the Ignore LAN traffic option. In this case NetWorx will merely collect network adapter statistics and memory usage should always stay low.
I'd suggest to turn off the Ignore LAN traffic option. In this case NetWorx will merely collect network adapter statistics and memory usage should always stay low.
Re: Possible memory leak 18 October 2016, 09:35 |
Registered: 7 years ago Posts: 8 |
Re: Possible memory leak 18 October 2016, 10:54 |
Admin Registered: 18 years ago Posts: 3 519 |
I am not sure if I understand what you said, but if the computer is connected directly to the Internet, there's really no point in having Ignore all LAN traffic checked. If you turn it off, you will lose the ability to track traffic by application, but shouldn't be any memory leaks.
We could make a debug version and run through a tool like Dr Memory, in fact you can do it even without debug builds - but I am afraid in the end we'll just find a buggy third-party DLL or something like that.
We could make a debug version and run through a tool like Dr Memory, in fact you can do it even without debug builds - but I am afraid in the end we'll just find a buggy third-party DLL or something like that.
firstrose
Memory leak? 08 November 2016, 18:00 |
Re: Memory leak? 08 November 2016, 18:22 |
Admin Registered: 18 years ago Posts: 3 519 |
As mentioned above, it could be an app that opened a lot of sockets, but not closed them for a long time. Try going to the Hidden Settings, set Keep track of TCP/UDP connections to False, and restart NetWorx.