Hey, I am decent with computers, but I am a newcomer to litestep, and I haven't fiddled with it much. I didn't see anyone say anything anywhere, but lately, this is a new phenomenon, my litestep is taking up HUGE memory, right now its 128,748k, of mem, JUST litestep.exe, let alone other things XP has running. I have been messing with my computer a lot trying to hunt and eliminate viruses and adware, so did I screw something up? It used to be a reasonable size.
Sounds like a memory leak to me. Does this happen with all themes? Try to comment out all your modules, then add them back in one by one until you find the culprit.
If the memory hog is "litestep.exe" from the process tab of the task manager, there is no blaming spyware as the culprit.
This will def. be a problem with a module you have loaded.
Try finding something that will jump the mem usage, and do as ilmcuts suggests. Keep the task manager up while recycling.
Another option could be to use aboutex and unload the modules through the GUI. That's not as thorough, but may be faster (watch for drop in mem usage)
I have this problem myself... just before I recycled litestep it was using about 200 megs of memory... now it's down to about 24... I am currently using Ivory... can anyone think of a module running in that theme that might be causing the memory leak?
You can indeed blame spyware if it installs a system-wide hook. Still, I'd think a memory leak in a module more likely than a hook in spyware only affecting one process.
So far the most obvious memory leaks I've encountered are the one in IconDesk if using hue/saturation and the one in XLabel if using it to display desktop icons.
People also say that Popup leaks if you use icons, but I can't confirm that.
Well there were cases of WindowBlinds causing the LS process to use several hundreds MB...
well for my system I don't use windowblinds and I'm certain there is no spyware on my system unless it can get past 3 layers of checking....
I have tried using the newest RC litestep and for a while that brought down the memory usage but now I'm back up to around 50 megs of memory being used... can anyone offer any suggestions about what I can do to try and fix this problem?
Standard bug-finding procedure: Comment out modules one at a time until the problem goes away.