memory leak in CIDLogSrv*32?

[lleo]

I upgraded to 5.2.1 maybe 1-2 weeks ago and shifted focus. My CQC server worked reliably in the background and no beat was noticed missing...

Today opened an RDP session to continue where I left it off 2 weeks ago to find that everything was sluggish again in the UI.
In taskmgr I am showing the CIDLogSrv*32 using >1.8GB of memory
The Admin Interface was open, but no other tab is viewed.
Starting the "Monitor the Logserver" shows not a single log entry.
I am sure I have events and actions which should be logged when invoked, but there is no driver with log verbosity high.

Any suggestions on troubleshooting this? Pretty sure restarting the Application Shell will fix it.

[Dean Roddey]

Let's keep and eye on it. But, in the meantime, stop the service, and delete everything out of the directory (on the master server):

[cqc]\CQCData\Logs\

Then start it back up. It will be back to normal again. Let me know if you see it again. This has happened a handful of times over the years, but it's so rare and un-reproduceable that I've not been able to chase down why it might happen.

There may have been something about the transition that confused it, i.e. some bug of old that caused the data to be corrupted or something. Starting it over should get rid of that possibility.

[lleo]

So I restarted the App Shell and that cleared the memory hold.
However, when I opened the Monitor the Log Server again, I got an error message with title "Unhandled system exception in GUI Thread" with red X icon and "No information available"
Something happened with my logging capability.

[Dean Roddey]

Delete the files as mentioned above.

[lleo]

I did it again, this time found a stray process that was keeping a file open, after killing that as well, now seems all is well.

[Dean Roddey]

OK. Just check it now and again over the next few days. It's unlikely it will happen again, but just in case.