Zugg Software :: View topic

Novice Joined: 21 Jul 2008 Posts: 41

I'm having memory addressing errors bigtime after upgrading to 3.32 . additionally, after getting these errors, parts of pkg files are blown away. This is getting seriously frustrating... Can anyone tell me where to start looking... I NEVER had this problem in 2.37

Do all pkg files belong in the packages folder, or should they reside in the session folder? I'm drawing for any ideas at all at this point

Beginner Joined: 02 May 2010 Posts: 14

This is a problem I'm having as well, and talking to multiple other cMUD users, it's apparently a widespread problem.

After a certain amount of scrollback happens, cMUD will freeze, spinning up my ram usages to 25% (I have 8GB) and all 4 cores of my processor spin up to about 50%.

Unfortunately, since most spam comes during major bashing and\or fighting, I end up dying a lot because cMUD completely freezes.

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

I can pretty much guarantee that both your problems are due to a corrupted layout, corrupted packages, and a corrupted mapfile. Check out the shift trick, XML export/import process, and the mapconvert utility to learn how to uncorrupt these files.

Novice Joined: 21 Jul 2008 Posts: 41

Posted: Tue Nov 23, 2010 5:00 pm

Shift trick: When viewing the Session window, hold down the SHIFT key and select the Open Offline action for your session. This will reset the window layout. Lots of window layouts in v2.37 were corrupted. So this is the first thing to try.

XML export/import: Open your session offline and go to the Settings Editor. Use the File/Export All command to export all of your scripts to an XML file. Now exit CMUD and go find your *.PKG file for the session (usually in My Documents\My Games\CMUD\SessionName\SessionName.Pkg). Delete or rename that *.PKG file. Now run CMUD and select Open Offline. CMUD will create a new *.PKG package for your session. Go to the Settings Editor and use File/Import to import the XML file that you previously saved.

This will recreate your package database. v2.37 had some bugs that could cause corruption of your packages in some rare situations.

Corrupted map: Download the Map Conversion program from the Downloads page on www.zuggsoft.com. Run it and locate the *.DBM map file that was converted to CMUD v3.x. Click the Repair button to repair this file.

Finally, if you are having trouble with CMUD freezing during a large amount of scrollback, that is usually caused by badly written scripts. Run the Script Debugger to see what scripts/triggers are running during your combat and track down the scripts that are taking the most time.

Beginner Joined: 02 May 2010 Posts: 14

I've done all of that, and I'm still crashing. (and I'm not using your mapper).

The specific message is: Out of Memory.

Which is about impossible with my system, considering I can edit HD video and run after effects at the same time. Hardware is *not* the issue.

I'm seriously thinking you've got a memory leak somewhere that after cMUD has been open for x amount of time, or processed too much too quickly, it starts freaking out. I dropped 20% Ram usage (about 2 GB) just by restarting cmud.

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

There's no memory leak, Dask, you've got badly-written scripts. Since you are neither the original poster nor have you provided any information about your CMud setup, the two major points I can think of are that you have triggers/aliases/events/etc running far more often than you realize or that you are always using by-value variable calls (essentially, every time you use @varname to refer to a stringlist or datarecord variable you are putting extra copies of the original variable into memory). Moderate- to large-sized stringlists/datarecords can eat up a LOT of memory in a hurry in this way.

Beginner Joined: 02 May 2010 Posts: 14

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Dask,
Can you upload your package to the package library? This way we can install it and see if we see anything that maybe causing your issues.

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

Posted: Mon Nov 29, 2010 6:19 pm

CMUD has no memory cap, but it is only single-core. So 25% on a quad CPU system would be normal.

Your "out of memory" error is coming from one of your scripts that has an infinite loop in it. It's not running out of "normal" RAM, but it's likely running out of stack space with an infinite loop.

Try running the Script Debugger window to see exactly what script is running, although it's possible your script might lock up CMUD before it has a chance to update the debugger window. The only other thing you can do is add #debug commands to your script to track exactly what it is doing.

Apprentice Joined: 10 Apr 2009 Posts: 145

I just got the "out of memory" error, so I checked task manager.
CMUD was using 605M working memory, 1.5G commit. Shocked

Can I find out why, or do I just have to restart it?

Posted: Mon Dec 06, 2010 5:01 pm

Sounds like you have a script with a problem in it. There isn't any way to determine what the problem is after the fact. All you can do is normal debugging techniques such as the Script Debugger and enabling/disabling scripts and watching the memory usage in the task manager to see which script is using up your memory. But that isn't the issue that the original poster is having.