My litestep used up 14mb memory at startup, but sometimes it used up 20mb at startup, isn't this some mysteries?... (Of coz under the conditon which I haven't edit the theme)
Hmm, I thought that was normal, my ls uses 14mb at startup too, but it jumps up to 80mb at times (mostly at 30-50mb after an hour or so of use). I'd always figure it was due to all the cached items of popups and labels.
LiteStep CAN user 20MB of memory on startup. That would depend on the modules starting and what it does at startup. LiteStep SHOULD NOT take 80MB of memory. The fact that it is increasing memory over time tells me you have a bad module configured. You really should do the basic troubleshooting and find out what it is.
Hmmm, could be. I'm not sure what is a "badly" configured module, I'm just following the module documentations. And I have no clue what basic troubleshooting would entail?
I suppose I could load and unload each module independently, and see if LS increases in memory consumption after 1 or 2 hours. But that would take a long time to go through the whole list of modules.
You misunderstood. Not that you configured the module badly...just that it is a bad module. For example...LSSlider can be crap based on how you configure it. Different versions of LSXCommand have some issues, same with vtray and a couple versions of label. You should strip LS down to the core components (Desktop and Hotkey) and slowly add modules back in. Start with the necessities like Popup and work towards the eyecandy.
Well I have:
As far as I can tell, all these seems like pretty well known and well used modules. Maybe multikey, wazup, systemevents, and lssyndication could be unstable, but they didn't strike me as obscure modules since there are multiple version of them.
As far as I can remember (I wasn't really paying attention at the time), it was only with Rainlendar loaded that my peak RAM usage went up to 80 mb. If it wasn't my peak usually stayed around 40mb, and the average was 30 or so (This is after 2-3 hours, and about 200 or so recycles later.
If you (or any experienced coder here) could give me a clue as which one is most likely causing the problem, it would be appreciated.
Otherwise I'm almost done with my current theme and I'll try disabling various modules and see what happens.
The real question is what are you getting after a few hours and no recycling. You really only recycle tons when building. I've had litestep taking up way over 130+ megs before from a memory leak in xlabel, which was reportedly related to transparent icons. You could see the memory footprint grow with each recycle. Right now I'm running that same theme, same modules etc, and it's only taking about 6.3 megs. My computer's been on all day.
Like DeV was saying, it could just be a setting in one of those modules.
You can't just assume that only obscure modules could be broken, or that modules that aren't released a lot are broken. Even good coders make dumb mistakes. I'd start with desktop, and jkey which is loaded in your step.rc, and go from there slowly including one module at a time. Eventually you will find your issue.
Thanks for the input, and I'll start testing these modules after I complete this current theme I'm working on.
^^Hmm, are you saying it's OK to get increased memory usage with a lot of recycling IF I don't get increase usage with no recycling? I currently DO have transparent icons in xlabel, so that may be the issue. Well the memory footprint doesn't grow proportionally after each recycle, but tends to go towards a max and then never goes above that, which is why I wasn't concerned at first, (but it might be just due to the fact my computer never stays on for a long period of time.) And if I don't do anything with my computer on with litestep itself (IE running bangs and opening popups), the memory usage doesn't increase much, so I can't just leave my computer on after a recycle, I'd have to constantly open and close stuff in the gui for an hour.
And I know definitely xpopup increases my memory usage everytime I open up a popup, but that's just due to caching the popups right?
^I'm not sure what jkey is, is that a better module than mkey? The only module I have loaded in step.rc is NLM right now. Would the j-modules (jDesk and jKey, etc) be more stable than the standard?
hmm, but even if I do find a bad module, it would be difficult for me to tell exactly what setting in the module is causing the problem? Do I just enable and disable each setting and try it? (That would certainly take forever), or should I just report it?
1) Yes and no. Increased memory usage after a recycle is a sign that a module isn't clearing out its memory upon recycle. However, sometimes it just happens...especially if you recycle over and over and over again.
2) No, your memory should not increase every time you open a popup. This would be a good place to start when looking for a bad module. Id check around to see if someone has also reported a bug with a xPopup setting.
3) jkey is loaded as part of OTS2. I thought that it was loaded by step.rc but I could be wrong. The j modules were released by jugg therefore they are the greatest modules ever written. :)
4) I would find out what module it is first. Once you do that disable any eye candy and see if that helps.
hmm, OTS2, do you refer to the Installer by Omar? Because I could not get that to work, so I basically salvaged what the installer did install (which was the directories, step.rc, and the personal .rc, the theme was corrupt, and I'm not sure if step.rc and personal .rc installed correctly) and built from that. Does that mean I don't need to include the jkey module in my Theme since that should be loaded through the personal directories?
EDIT: Something's definitely up with xpopup on recycle, I just reloaded the xpopup module with !xpopuprescan, and my memory usage jumped up by 4-5 mb. But on a good note, the memory usage doesn't seem to increase if I don't recycle constantly.
You may want to hop on IRC and talk to some of the people in #LiteStep to see if they can get that install working for you. If something was missed it will hurt you bigtime in the long run.
Try loading a different version of xPopup and see if that fixes your problem. Then send a bug report off with your config so that it can be confirmed and corrected.
Well, I am doing OK right now with LS, and I'd rather not mess with the installer right now (Even though it probably will be a good idea, why fix what's not broken, maybe after I finish this theme)
As for xPopup, I'll see about reporting the bug. I'm still not sure what makes the 4-5 mb spike, but it doesn't happen every recycle. I'll have to pay more attention to it.
Just a hunch...try disabling popup icons if you have them enabled.
Hmm, it happens rarely, I don't think it's actually a problem with xpopup on recycle anymore. I think something might be wrong with the rescan bang, but I'm not using that at all, so I'm not going to worry about it.
The problem was with Rainlendar
Here's a pic of my Ram Usage after 3 hours with constant recycling:
I suppose I should post or email the creator with my step.rc config?
(There really wasn't much I could config with Step.rc)