Stormfront memory consumption issue - private working set > 1GB

[Eodus]

Wasn't sure exactly where to post this, but figured most anyone browsing this section will have some kind of development background. The issue I'm having is this... I open Stormfront, memory consumption is fine... open the task manager, look at memory/CPU details, and I can watch the memory private working set steadily increasing in Stormfront. The other day, after leaving it open for about 36hrs or so, it had exceeded over 1GB of working memory, causing noticeable lag, slowdowns, overall delays/issues.

I'm running Windows 10, with an I7 processor, and 64GB of RAM. I am running Lich, but none of the Ruby processes really seem to fluctuate. Haven't had a chance to test in any other environments. Anyone else out there who can report similar results?

[Mogonis]

Stormfront leaks memory. Annoying but kind of stuck with it.

[Eodus]

Here's a useless question: why hasn't anyone fixed it? And, a few semi-useless ones: is there a Lich-compatible alternative to Stormfront that I am not aware of? Is Wizard FE compatible with Lich?? I've always just assumed it was legacy.

[Velfi]

Wizard works with lich, and Tillmen also wrote his own FE, Profanity (http://forum.gsplayers.com/showthread.php?83636-Profanity-a-terminal-frontend).

[Eodus]

I'll give them both a whirl. Think I'll start with Profanity. How far along is this thing in development? Do you have a preference yourself?

[Velfi]

I'll give them both a whirl. Think I'll start with Profanity. How far along is this thing in development? Do you have a preference yourself?

I prefer SF for a few of its features, but I don't use it over the periods of time where it becomes a noticeable problem. I only know of Profanity, you'll have to read through its thread for its current status but I believe it's at least usable, maybe missing some of its planned features, not sure.

[Eodus]

After becoming pretty used to StormFront, I gravitated back in that direction. So, figured out a solution to the memory consumption issue. Picked up a pro copy of Process Lasso and set a watchdog rule to trim the virtual memory associated with Stormfront.exe if the private working set (need to indicate this specifically on the memory type selection) exceeds 25mb. Also elevated I/O, power, and what are most likely to be a bunch of other B.S. settings which seemingly have improved overall performance. But the memory leak is no longer an issue.

[Eodus]

Okay, it could be the serious number of beers I've had this evening, but this solution has improved every aspect of functioning within the StormFront terminal. Timing issues I had previously with XMLData / RT misalignment == gone. Overall significantly, significantly smoother experience. Again, might just be the beer.

[Tgo01]

Okay, it could be the serious number of beers I've had this evening, but this solution has improved every aspect of functioning within the StormFront terminal. Timing issues I had previously with XMLData / RT misalignment == gone. Overall significantly, significantly smoother experience. Again, might just be the beer.

Pretty awesome if you fixed the SF memory leak on your end, that was one of the reasons I moved away from SF.

[Eodus]

Pretty awesome if you fixed the SF memory leak on your end, that was one of the reasons I moved away from SF.

Continuing to test the validity of the above statements. But initial results are looking good. Looks like the free version should include everything required to set the watchdog rule. Not sure if it's a time limit or whatever -- I'd used it in the past so knew it was pretty legit.

[Eodus]

Appears to have resolved the issue. Couple tweaks... change watchdog rule to trim at 75, not 25mb. And exclude from ProBalance restraint and smart trim. Running smooth as butter over here.

[Eodus]

Confirming that after a week and a half of testing that things are running smoothly. The StormFront memory leak is solved, and running predictably well. My settings:

Stormfront.exe
- Priority, I/O = High
- Application Power Profile = Highest Performance
- Exclude from ProBalance Restraint = Checked
- Exclude from SmartTrim = Checked
- Classify as Game (probably not necessary)
- Watchdog Rules: trim virtual memory when private memory working set > 100mb for > 1sec

rubyw.exe:
- All of the above, but not classified as game, and no watchdog rule

[SashaFierce]

This was hugely helpful to me. I ran into the same problems because I don't log out.

[Soulance]

I'm going to have to try this out. Is this found under the "properties" menu?

[Eodus]

I'm going to have to try this out. Is this found under the "properties" menu?

Accomplished with a downloaded programmed called Process Lasso that runs in the background. You can download a free copy from BitSum. I got the pro version, though pretty sure the free version would work just as well.

[Soulance]

Accomplished with a downloaded programmed called Process Lasso that runs in the background. You can download a free copy from BitSum. I got the pro version, though pretty sure the free version would work just as well.
Excellent, thanks for the info. I'll give it a try.

[Allereli]

Set it up as you described, except I'm not sure if I got this one right. Maybe because I wanted to try the free version first.


- Watchdog Rules: trim virtual memory when private memory working set > 100mb for > 1sec

Here's my screenshot for what I did for this. There was no private memory option, just virtual memory and CPU, which changed the memory to a percentage.

8111

[Soulance]

Set it up as you described, except I'm not sure if I got this one right. Maybe because I wanted to try the free version first.



Here's my screenshot for what I did for this. There was no private memory option, just virtual memory and CPU, which changed the memory to a percentage.

8111
I think it was said that you don't want that watchdog rule for ruby though. That one is only for SF. Otherwise, that's what mine looked like too.

[Allereli]

I think it was said that you don't want that watchdog rule for ruby though. That one is only for SF. Otherwise, that's what mine looked like too.

good point! because I stop reading after I do the first thing :)

[SashaFierce]

I have the free version as well, it's been working great.

[Allereli]

I have the free version as well, it's been working great.

nice. I don't even stay logged in, I just get memory alerts every few days and I have to reboot. I shouldn't have to reboot that much.

[Latrinsorm]

Am I the only one suspicious of someone with an Evangelion avatar offering up a computer program that magically makes everything better? Second Impact here we come T_T

[Gelston]

nice. I don't even stay logged in, I just get memory alerts every few days and I have to reboot. I shouldn't have to reboot that much.

I was trying to figure out wtf llamas and the Yankees have to do with eachother, and found out the scientific name for llamas is lama glama. I am happy with this information.

[Allereli]

I was trying to figure out wtf llamas and the Yankees have to do with eachother, and found out the scientific name for llamas is lama glama. I am happy with this information.

I'm happy with that information, too. Oddly, the Yankee llama is from a Bank of America ad.

[Eodus]

Am I the only one suspicious of someone with an Evangelion avatar offering up a computer program that magically makes everything better? Second Impact here we come T_T

Shhhhh lol :)

[Goat]

I tried Process Lasso to no avail. Oddly, it was showing all my CPU cores as nearly pegged just from watching a streaming video in chrome. I Googled around for a bit and someone mentioned that they cleared up a similar problem when they realized their CPU fan wasn't working, putting their CPU temps at unsafe levels. I downloaded HWMonitor; lo and behold the core temps were around 90C. I opened up the case and found that the my CPU fan was running but had come somewhat loose from the CPU itself. I pressed it back down and now the temps are in normal-er ranges. It would probably be smart to get a new fan (I think it could easily come loose again), but it's working well for right now.

Not hating on process lasso or anything, I'm sure it's been a big help for people in this thread. I just turned out to have a different problem - something else people might want to look into if process lasso isn't cutting it.

[Soulance]

I tried Process Lasso to no avail. Oddly, it was showing all my CPU cores as nearly pegged just from watching a streaming video in chrome. I Googled around for a bit and someone mentioned that they cleared up a similar problem when they realized their CPU fan wasn't working, putting their CPU temps at unsafe levels. I downloaded HWMonitor; lo and behold the core temps were around 90C. I opened up the case and found that the my CPU fan was running but had come somewhat loose from the CPU itself. I pressed it back down and now the temps are in normal-er ranges. It would probably be smart to get a new fan (I think it could easily come loose again), but it's working well for right now.

Not hating on process lasso or anything, I'm sure it's been a big help for people in this thread. I just turned out to have a different problem - something else people might want to look into if process lasso isn't cutting it.
Always good to check. And while you're at it, blow out the heat sync with some air as they're usually clogged up with dust.

You could also go further and pull the sync off the processor, clean off the old crap, and put new grease on there.

[Ltlprprincess]

So after a night of constant disconnects during a capped raid of Reim, I'm trying this. Wish me luck.