Zugg Software :: View topic - [2.18] Crash when zoning while speedwalking

Apprentice Joined: 11 Oct 2007 Posts: 154

This is another unrelated error I get after upgrading, it happens on a speedwalk when it goes from one zone to another.

Posted: Sat Dec 15, 2007 6:04 pm

Hmmm, not 100% sure what's happening here. Do you have any room enabled? Is it any zone crossing, or just a particular one? Did you run the compatibility report to check for any problems (it also has the side effect of recompiling all of your scripts)?

Apprentice Joined: 11 Oct 2007 Posts: 154

Do you have any room enabled?
What do you mean by this?

Is it any zone crossing, or just a particular one?
Any zone crossing, however i can manually press direction to cross zone, its only when a speed walk between zones is trying.

Did you run the compatibility report to check for any problems
No problems found.

Apprentice Joined: 11 Oct 2007 Posts: 154

I downgraded version by version untill I found one that did not cause this error, the problem was gone once i reached 2.14a.

The versions that did not cause the crash were versions 2.05-2.14a

Apprentice Joined: 11 Oct 2007 Posts: 154

Going even farther back to resolve another issue, I found that switching zones also causes this crash in 2.04 - 2.00

Posted: Sun Dec 16, 2007 12:25 am

I meant to say 'room scripts' enabled.

I'm not sure why zone crossing were the problem but you probably don't want to go back to a beta version. It's an odd thing, compacting the map does help sometimes.

Is you mapper window docked? Are you using multiple monitors? Any theming engines like window blinds?

Did you try disabling your map related triggers?

Apprentice Joined: 11 Oct 2007 Posts: 154

Not using any room scripts

Version 2.14a is now the version i went back to, im able to stably play. compacting the map did not fix anything.

mapper window is docked. not using multiple monitors, no theme engines, for the most part its a fresh install of windows with all windows updates.

I have disabled ALL scripts i use to make sure this was not the issue.

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

Hmm, there was an old bug where zone crossing crashed CMUD all the time, but that had been fixed. Haven't tested my own yet.

Apprentice Joined: 11 Oct 2007 Posts: 154

OK so i did some further testing, I really really really would like the opportunity to be able to use the newer cmud but im still crashing when i go from one zone to another on a speedwalk.

So i made a NEW character on aardwolf, changed 2 character settings:

brief 2 (hides room description unless manually typing look)
prompt [ %h/%Hhp %m/%Mmn %v/%Vmv %Xtnl] >%c (only difference from standard prompt is carriage return on the end)

I then configured the mapper with the autoconfig wizard where it goes south and waits 5 seconds, I unchecked description, since i dont map those.
Also I went into the config and unchecked "Allow blank line to trigger speedwalking as prompt" (this makes directions wait for the prompt when in slow walk mode)

Next I opened a NEW map and mapped several rooms, i put a couple rooms into their own zone. so now i have two zones

Next I attempted a #walk to the other zone. AND i get the crash message thing, this happens regardless of speedwalk mode i am in.

ALSO the strange thing is when it pops up the error message i can click continue application and everything actually seems to be working just fine.

I can send you both the new settings and map database i have created if anyone would like it.

Would really like to figure this out.

After doing these tests with version 2.18 I downgraded to 2.14a which is the latest version i can use without getting these error exceptions.

Wizard Joined: 14 Oct 2000 Posts: 1368

Wizard Joined: 14 Oct 2000 Posts: 1368

The file you sent me appears to work. It speedwalks on the map through zones. Something you can try is to connect "offline" and try speedwalk then. Does that work?

Edit: I have also tested to make similar map setting described in your post on Aardwolf(near the starting rooms) and tried speedwalking online. That also seem to work between zones.

Apprentice Joined: 11 Oct 2007 Posts: 154

could this be crashing because of my computers files? like the drivers i use for my hardware, etc?

I dont know anything about debugging access violations... but there has to be an explanation why it works with 2.14a and not 2.18

Wizard Joined: 14 Oct 2000 Posts: 1368

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

I have noticed a few errors when speedwalking across zones in this version. If I continue though there isn't any problem.

It is a sporadic thing for me however. I will see if I can find a case that I can narrow down the cause for this evening.

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

Well, it turns out that this was someone else's map and that the errors were occurring in rooms with Room scripts in my case so I guess I'm no help here sorry.

Apprentice Joined: 11 Oct 2007 Posts: 154

Cmud version 2.14a seems to be a pretty solid version. I think i can live with using this version for now, ill just wait till the next version to see if anything has changed. If anyone needs any more information concerning this crash let me know, if not im content for now with this older version.

Posted: Mon Jan 07, 2008 10:13 pm

v2.14a certainly isn't "pretty solid". There are many problems related to the Threading system in CMUD that will cause you sporadic crashes in that version.

According to your crash dump, you have a trigger running when you cross the zone boundary and that is where the crash is happening. Try disabling all of your triggers and then enable them one by one in v2.18 to determine which one is causing the crash.

On the MUD that I play I have hundreds of zones and am crossing zones with speedwalks *all* the time and don't have any problems. So it's not the zone that is causing the problem...it's an interaction between switching zones and having one of your triggers fire at the same time.

Posted: Mon Jan 07, 2008 10:30 pm

I've have this crash on zone transition as well, but I hadn't had the time to debug it as much as Xekon. The particulars he mentioned match my situation perfectly. I believe I've sent in a few crash logs when this has happened so perhaps there are some similarities that can be seen between the two.

Posted: Mon Jan 07, 2008 10:57 pm

If this happens, then I'd need to see the exact trigger that is causing the crash. The Crash Dump report (like the one shown above) only shows me that a trigger was executing...it doesn't give me the script of the trigger that caused the problem.

Apprentice Joined: 11 Oct 2007 Posts: 154

I have a folder called "system" in my settings, no doubt I got it back when I was using an older version of zmud or cmud.

If I disable this folder than CMUD does not crash between zones, HOWEVER without this folder the automapper does not keep up.

For Example:
If I move one room, wait for mud output, then move one room, wait for mud output etc, then the automapper works.

But I tend to move more quickly than that, I will hit wwwseesw because I know exactely where this will take me in the mud, with the system folder enabled the automapper is able to keep up with multiple directions sent at once but without the sytem folder the automapper does not track correctly, it moves one room on the map and then gives up tracking.

Also I should note that I have tried right clicking on and disabling the system folder and then reconfiguring the mapper, but it does not solve the issue of not tracking.

To be perfectly honest I had given up on using the new version of CMUD and have been using cmud 2.14a happily since I last posted without any issues at all, however I am now trying to use CMUD under Linux Ubuntu and from what I hear it works better with the theme engine removed so I am once again trying to use the newer version of CMUD. Please help me out, if you require me to track anything else down I would be more than happy to.

Below is the exported XML for the folder "system" from my settings:

Posted: Thu Feb 14, 2008 1:18 am

I had this error as well and for me it went away when I unselected "Match Room Name" in the mapper settings. I then had to substitute some other method of sending an "#OK" when a successful room change had occurred.

Apprentice Joined: 11 Oct 2007 Posts: 154

Interesting got any good ideas for sending #ok?

Posted: Fri Feb 15, 2008 3:41 am

In Achaea with ATCP support this was pretty easy, but in general if your MUD has a unique line for the room name you can trigger off of, you can use that. There seems to be something associated with CMUD doing the regex search for the room name which was causing the problem for me. When I made a trigger for the room name and put an #OK in it, it worked fine for me thereafter.