Memory usage by WUHU
- Has anybody seen a memory leak running WUHU?
I am running version 188.8.131.52 on Windows XP, and it periodically stops reporting data, due to a memory allocation error.
Restarting it fixes the problem. Last time, prior to restart, I looked at the memroy usage, and it was over 500 MB,
as reported by the Task Manager. The new process (right after a restart) shows a bit over 25 MB. After several hours, it's now
340 MB (still working). Sounds like a memory leak.
Note, I was previously running a version .184, on Vista, so a couple of things changed. On Vista, I had not seen such behavior,
even after continuously running WUHU for several weeks at a time.
- Okay, with the file path corrected, the memory usage grew by about 4MB in 24 hours from startup; 16 to 20MB.
This is running .198. It's more than an order of magnitude better than before.
The growth may be attributed to me using graphs and wind rose -- it seemed to increase the first time I used those,
and then stabilized. I think the problem is solved. I am now going to restart using .200.
.200 is 24 MB right after startup.
On 2011-10-29 13:59, wuhu_software wrote:Well that helps explain a lot.As it turns out, the Microsoft MFC library was throwing exceptions. Although the exceptions were caught, preventing a program crash, the memory associated with the exception was not released back, resulting in memory leaks. Because there were many many attempts to write the currdat.lst file, as it can be hundreds of lines, many leaks happened.I have gone through the code and released the memory when these file exceptions occur.Thanks for getting to the bottom of the problem.See:
--- In email@example.com, David Lipper <glenvilleweather@...> wrote:
> An excellent suggestion! I did that, and collected a large number of events.
> On first examination, I found that many of them were failures to write to the OutputDataFilePath,
> which was a setting in "WUHU Configuration Data.ini" I left when copied from another computer.
> The path did not exist on the new computer, so it could not open it.
> I changed the setting (required me to exit the program; start/stop did not work).
> Now, those error events are gone, and the computer seems (subjectively) less loaded.
> I still do see some errors in the event log like RegQueryValue and RegOpenKey returning NAME NOT FOUND.
> The keys in question are ...\EnableAutodial and ...\Http Filters\RPA. I assume these types of errors are okay?
> Memory usage is a bit less than 15+ MB at the start. I am hopeful that it will not grow without bound.
> Thanks again!