Memory Leak

[GoogleCodeExporter]

I just downloaded 4.5.1 64Bit to use on my Orange monochrome G15. After about 
10 minutes i had opened task manager to look at some processes and top of the 
list was LCDMisc at 800MB. I restarted the Logitech manager and LCDMisc and i 
started at 50MB and is now above 500MB and climbing as i write this. This is 
one Win 7 Professional X64.

A little frustrating, love this app but cant do any development when 1/4+ of my 
RAM is going to a screen app.

Original issue reported on code.google.com by mike.con...@wiredbyte.com on 30 Nov 2010 at 3:23

[GoogleCodeExporter]

Have you tried running "lodctr /R"?

Sometimes performance counters break in some manner, and that command rebuilds 
them...or something.  LCD Miscellany has a leak somewhere when they're broken, 
though as I don't have any clue what actually happens when they're broken, it's 
kinda hard to debug.  Suspect there's some exception somewhere that Microsoft 
silently catches for me, leaking a fair chunk of dynamically allocated 
memory...But I could be wrong.

Probably should have used smart pointers, but too much effort to go back and 
change everything now.

Original comment by mattme...@gmail.com on 30 Nov 2010 at 3:29

[GoogleCodeExporter]

Well it looks like it stopped the memory climb. I'll keep an eye on it and let 
you know if anything happens..

Thanks for the speedy reply.

Original comment by mike.con...@wiredbyte.com on 30 Nov 2010 at 3:37

[GoogleCodeExporter]

I also experienced this memory leak... except I now primary use the computer it 
happened to as a server. Funny story; for the last week all the remote services 
on the machine would turn themselves off one by one... first ssh was 
inaccessible, then vnc, then hours later, hamachi; one by one. I was very 
confused! One of the times I went around to rebooting it, it was still 
functional enough to wake the monitor out of standby and show a low on memory 
warning.. after a reboot I traced it back to lcdmisc64. I guess it was 
requisitioning all the ram and slowly kicking every other process out of the 
system XD

An important distinction is that this only started happening since I unplugged 
my G19 and sent it back for replacement; I have used this same version of 
lscmisc for weeks without problems or reboots.

Well, hope that sheds some light on the situation. If it only happens when no 
lcd is available then that's not really an issue; just reporting my findings 
here.

Original comment by link68...@gmail.com on 11 Dec 2010 at 3:27

[GoogleCodeExporter]

I've been thinking about auto detecting the leak...Not a solution, but not hard 
to check every couple minutes.  If detected, can either pop up a dialog, or 
just run the line myself, and restart.

Original comment by mattme...@gmail.com on 11 Dec 2010 at 6:38