Zugg Software :: View topic - [2.02] Urgent

Wizard Joined: 14 Aug 2004 Posts: 1269

I have just submitted two separate 100% reproducable crashes with steps from a blank session using the #WINDOW command (with no other commands or output!).

I also submitted a few days ago a crash that is the same as one of the above #WINDOW crashes, except that the Window was created with the #CAPTURE command. One of these crashes causes your package to be in a state where it will get an Access Violation every time you open it, so I consider this bug to be a fairly critical one.

Apprentice Joined: 13 Aug 2007 Posts: 166

I use both commands alot, so I also hope it's possible to remove the bugs :P

Wizard Joined: 14 Aug 2004 Posts: 1269

I think the more serious crash of the two is now fixed in 2.03 even though it was not mentionned in the version history. I've resubmitted a crash report for the other one.

Posted: Mon Sep 10, 2007 8:31 pm

Can you post the procedure here for people to try and confirm? I've got a lot of reports in the crash database and if you have a way to reproduce this, then it's always good to post it here for people to test. I just did some basic playing with both #WINDOW and #CAPTURE and didn't get any crashes here.

Wizard Joined: 14 Aug 2004 Posts: 1269

100% reproducable steps in 2.02 and 2.03:

1. Open CMUD
2. Close the Sessions Window.
3. #WINDOW Tells blah
4. Optionally, turn on status bar and command line in Tells window (my default had them switched off now, but this step is optional).
5. Click in the Tells window - the critical part is for the Tells window to have focus when doing the next step, but you can just click in it.
6. Save Session as Tells
7. Crash.

100% reproducable steps in 2.02, but I haven't yet reproduced it in 2.03:

1. Open CMUD and Close the Sessions Window.
2. Enter this command into the command line:
#WINDOW Tells blah
3. Turn off the Status Bar and the Command Line (I don't know which of these causes the problem) if they are on.
4. Save Session as Test.
5. Close CMUD with the red X
6. Reopen CMUD
7. Open the Test session offline - the database window pops up for a second - I don't think it should be - separate bug?
8. Crash.

Note that in 2.03, the database window does not pop up for a second when I replay these steps - maybe this is why it doesn't crash?

Posted: Mon Sep 10, 2007 11:59 pm

Ahh, ok, I see what you mean now. When you Save a session, CMUD assumes that the window with the current focus is the "primary" window associated with the session. I think that is causing the problem.

As long as it works fine when the main window is selected before saving, then it's not as critical as I feared from your subject title.

Wizard Joined: 14 Aug 2004 Posts: 1269

Yeah, it was the 2nd one that was more critical because it was making my package unopenable if I ever forgot to close the tells window before closing CMUD.

Wizard Joined: 14 Aug 2004 Posts: 1269

[quote="Seb]100% reproducable steps in 2.02, but I haven't yet reproduced it in 2.03: [/quote]
Still haven't reproduced it in v2.03, but I am slightly concerned this bug may reoccur on another later version since there was nothing in the Changes log about fixing it. I noticed in v2.02 that it always opened the database window after I opened my session, even though I would shut it each time. I think maybe you had saved 2.02 with the database window open and that was causing this bug.

Actually, I think this bug may also have been in some of the early 1.0 betas too, but then there seemed to be so many issues with #CAPTURE back then (immediate crash) that I can't be sure if it's the same.