Zugg Software :: View topic

Posted: Sun Jan 31, 2010 11:29 pm

Since updating to 3.13, I've seen my RAM go from 65-80MB to 150MB of RAM being used. Not sure what's causing this, but I wonder if others have noticed the same thing...

Charneus

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Is this pre-converted map or post? And how massive are your scripts? I'm still at 85k and 2k for the security module, myself.

Posted: Mon Feb 01, 2010 12:12 am

Pre-converted map. Scripts haven't changed any since 3.12, but I do have 1600 triggers (half of the classes are disabled at any given point of time) as well as 550 aliases and 860 variables It's never gone above 85 for me, though, in any version.

Charneus

Posted: Mon Feb 01, 2010 11:54 am

for me it eats up my cpu at points, i dont look how much ram its using though, its to the point where if i leave cmud on for 5 hours take a nap come back and its frozen

Posted: Mon Feb 01, 2010 6:20 pm

Hadar: Please only respond to a post if you are experiencing the same issue. You already reported your freezing issue in another post and without ram usage information it doesn't have anything to do with this post.

As far as the memory issue, does the memory keep going up? It's only a memory leak if memory keeps going up and up until it uses all of your system resources.

Otherwise you will need to do more work to track this down as I'm not seeing any RAM problems in my sessions. For example, try your session without a map. Or try exporting/importing your session XML to a new session, etc.

Posted: Mon Feb 01, 2010 7:07 pm

It steadily increases. It'll start out at about 70MB or so, and after about an hour or two, it's up to 150MB. I'll try without a Map first, then try a new session, though I'm not sure what would be causing it. :\

Charneus

Posted: Tue Feb 02, 2010 9:44 pm

Could this be the cause of the memory leak? I keep getting this error when opening CMUD, and nothing seems to fix it...

Posted: Tue Feb 02, 2010 11:31 pm

That's an error in your layout file. Try holding down the SHIFT key and connect to your session to make a new layout file. From the crash dump, it looks like a command line that has gotten detached from it's proper window, or is on a hidden window of some kind.

Posted: Tue Feb 02, 2010 11:32 pm

In fact, I'm kind of interested more in this. Would it be possible to send me the *.PKG, *.XLY and *.TBZ files for this session before you fix them? I am experimenting with the idea of trapping/ignoring all crashes from the window and toolbar layout components to see what happens.

Posted: Wed Feb 03, 2010 12:04 am

hmmm, if your going to be playing with the layout stuffs, maybe you could add a backup/restore feature, 2 additional times in the layout menu, that way players could backup a layout immediately after getting it set up nice then if something happens to layout they can just restore a nice new layout. when you get 10+ windows funny things start happening to those files and it can be annoying to re set up all of your windows.

Posted: Wed Feb 03, 2010 12:22 am

Crap. I had already fixed it long before you even posted the solution, since I figured it was a layout issue after looking over the stack. Funny thing is, it happened once after I did the shift-open. Then I used the map converter to convert the map back to zmud, then convert it back to CMUD, and it started working again... If it happens again, I'll definitely send the information to you. Sorry! :\

Charneus

Posted: Wed Feb 03, 2010 12:25 am

Yeah, but if you get too many backup files, then it gets pretty worthless too. What I usually recommend is to save your layout and then leave the "Auto Save Layout" option turned off and only manually save your layout when you need to.

In general, I am as unhappy as anybody by the lack of reliability in the window and toolbar layout features. Unfortunately, it's the Developer Expression and AutomatedQA components that are in charge of that (which is why each layout has a separate file and separate formats). None of these components were really designed for user-level layout save/restore like CMUD has. It's just so easy to get unattached toolbars, or hidden/ghost windows that don't go away and just keep getting saved in the layout leading to later corruption.

But I don't even have a good understanding myself as to what generally causes layout file corruptions. The errors in crash dumps are usually buried really deep in the 3rd party code. Look in the crash dump above and look at how many levels into the "dxBar" module the crash occurred. That's the Developer Express ExpressBars component for menus/toolbars. It's nearly impossible for me to debug 3rd party code that many levels deep. ExpressBars has a really unusual architecture that I mostly hate, but it's the only menu/toolbar system with runtime end-user customization, so we are stuck with it.

That's why I'm giving serious consideration to trying and trap and ignore errors when loading a layout. I don't know if that will cause the entire layout to abort, or if I can make it just abort loading whatever specific piece is corrupted, leaving it in it's default layout location. I need to experiment with some corrupted layout files to see if ignoring the errors helps or hurts. All I can say is that more than 50% of the crash dumps that I get are related to the layout system, so it's a pretty annoying issue for everybody.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

OK, so what about asking if we want to back up a working layout. Then when you trap one of these exceptions restoring that backup?

Then if it fails with that layout apologize and tell us that you are loading a new blank one?

Posted: Wed Feb 03, 2010 5:24 pm

I don't typically like popup prompts like that, especially in the middle of loading a character session. However, the idea of keeping a backup of the "last working layout" and restoring that if the load layout fails rather than just loading a default layout is a good one. I'll continue to think about how best to improve this.

Posted: Thu Feb 04, 2010 12:40 am

I think the ANSI coloring bug might have been causing this increased memory usage. Hopefully fixed for the next version.