Zugg Software :: View topic - [2.18] Crash crossing zone speedwalking, Fresh install, character, map

Apprentice Joined: 11 Oct 2007 Posts: 154

I have been having this problem for longer than I can remember.
I have been using version 2.14a because it is the latest version I could find that I dont have this problem.
This could be specifically related to the hardware or drivers my computer uses, who knows, however I would really like to figure this out.

I did a fresh install of cmud 2.18.
Created a NEW character on Aardwolf mud.
Created a few new rooms in a few adjoining zones.
Attempted to speed walk across zones, my location was correct on the mapper, I opened a different zone and double clicked on a room to speedwalk to it.

Here are some of the steps I performed below:

automap (disables mud automap)

brief 2 (disables mud room descriptions)

#KEY KEY9 {up}
#KEY KEY3 {d}

prompt [%T %h/%Hhp %m/%Mmn %v/%Vmv %Xtnl] >%c (adds carriage return to end of prompt)

down

open automapper

menu > config > reconfigure

uncheck room description
next
finish

Beginner Joined: 17 Jan 2008 Posts: 10

I can not add much to this great bug report other than saying that I see the exact same issue on a different mud (lusternia with ATCP enabled). I have been doing all of my mapping in one zone to avoid this for now.

Apprentice Joined: 11 Oct 2007 Posts: 154

what is ATCP?

Posted: Fri Feb 22, 2008 12:41 am

I also have had this problem, but only recently. Thought it was several new triggers I had made but removed them and that wasn't it. I have noticed that about half of my zone links will cause this problem but not all, and I have a few room link between rooms in the same zone that will cause the same issue. I have had the problem walking in fast safe and slow speedwalk modes as well.

Enthralled - augh I couldn't immagine mapping in the same zone, that would drive me crazy, I coudn't see anything, *comfort*

Posted: Fri Feb 22, 2008 12:58 am

xekon: see the help files.

Posted: Fri Feb 22, 2008 1:14 am

Xekon can you PM me and send me your test map I'd like to try and recreate the problem on my end.

Apprentice Joined: 11 Oct 2007 Posts: 154

PM SENT

Apprentice Joined: 11 Oct 2007 Posts: 154

*cry* I hate not being able to use the latest version.

I was able to export my settings and test them on a friends computer, and I was able to use the latest version of zmud no problem. I can only guess that the problem lies with software on my computer, drivers, or hardware specifically. There is nothing special about the software on my computer, I have formatted twice and tried the latest version of zmud twice soo my guess lies in the hardware or drivers my computer uses.

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

Interesting. I was not seeing this problem until recently, and now it is perfectly reproduceable. Zone-crossing crashes began to occur in the last few days when I was working on scripts related to room detection (#tagging lines, capturing room info, etc.)

I did a fresh install of CMUD on a second machine, moved all my packages across in XML (and imported them). Same result.

I disabled the entire module in which I had recently made changes. Still crashes.

I made a completely new session, with no packages, no map, no nothing. THAT doesn't crash. Smile

Added the map window to the new, empty session, loaded the map DB and settings (.zfg file), and stepped across a zone boundary. Crashes.

So I deleted the map and config, grabbed a clean copy of the map from my zMUD install, loaded it in the empty session, and reconfigured. Crashes.

So it's not related to my packages...it's related to the automapper and my map. Or possibly my map config, though it would have to be something recreated by the re-config process. And it appears to be the same stack trace as in the OP.

Fortunately, automatic bug report sending worked this time, so Zugg should have the report in his inbox.

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

Update. I created a new MAP FILE, mapped a few rooms, then moved some rooms to a new zone. I can walk across that zone boundary with impunity. It's looking very much like a problem with the map DB file itself, or at least triggered by it.

Could size be an issue? My normal map DB file is around 13MB, and nearly 11,000 rooms. I'll e-mail Zugg a link to my map file on a web server, since regular e-mail generally won't handle a file that big.

Also, speedwalking is not required (for me). The crash occurs even if I'm single-stepping by typing 'e' to cross the zone boundary.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

Ignore that. Stupid file sizes

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

Still present in 2.20 Beta. I've started a new thread on the Beta board to cover this.

Posted: Tue Mar 18, 2008 12:24 am

My experience is that cMUD will crash for no obvious reason while speedwalking. It happens to me every session. Sometimes it happens on my first attempt to speedwalk. Sometimes it takes hours for it to occur. Sometimes, it is the parser that crashes when attempting to speedwalk. By this I mean that the parser error box will pop up and inform me that it has crashed while parsing the alias that does my speedwalks. Now, what I do about it is ignore it. I know this is not the best practice but if I didn't do it this way, I would be restarting cmud every half-hour or so. Ignoring the error and continuing the application when speedwalking bombs the client doesn't seem to have adverse effects. Of course, I have no proof of this.

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

As I've detailed in the other thread on the Beta board (see my link above), my crash is completely correlated with a particular setting in my .ini file, and is completely reproduceable (I can crash the client at will in about 10 seconds, most of which is spent loading my map). The stack trace looks similar or identical to the one in the original post, so I'm betting that it's the same issue.

For those who are NOT following the other thread...my crash disappears competely if I uncheck the 'Wait for prompt in SAFE speedwalking' checkbox in the 'MUD Prompt' tab of the mapper config dialog. (I use safe speedwalk mode by default).

Apprentice Joined: 11 Oct 2007 Posts: 154

!@#$)_@_$#%($#()% SOLVED !@#$)_@_$#%($#()%

The problem was corrupted files in the packages folder.
Reinstalling Cmud was not solving the issue.

SOOO I delete ALL FILES in the packages folder, I then copied the 4 files my buddy had in his packages folder into mine. BAM problem SOLVED