 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Fri Oct 12, 2007 5:04 pm
[2.05] Crashes when closing session
|
I found two different ways to cause some rather nasty crashes when closing the session. One results in a crash dump, another causes a hard crash.
Procedure A crash dump
1. Launch CMud
2. Close Sessions Window (ESC)
3. Open Package Editor (CTRL-G)
4. Select File|Remove package from the Package Editor Menu
5. Close Package Editor with X button
6. Close Session with X button
| Code: |
date/time : 2007-10-12, 13:03:36, 386ms
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 24 days 6 hours
program up time : 23 seconds
processor : AMD Athlon(tm) Processor
physical memory : 109/383 MB (free/total)
free disk space : (C:) 14.11 GB
display mode : 1024x768, 32 bit
process id : $170c
allocated memory : 24.96 MB
executable : cMUD.exe
exec. date/time : 2007-10-05 13:48
version : 2.5.0.0
madExcept version : 3.0b
callstack crc : $694b753e, $8a8450ea, $8a8450ea
count : 2
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 009B393C in module 'cMUD.exe'. Read of address 0000003C.
Main ($1784):
009b393c +040 cMUD.exe OptionDat 1226 +2 PrefData.SetPref
009b3c27 +033 cMUD.exe OptionDat 1264 +1 PrefData.SetPrefBool
009b0fd7 +007 cMUD.exe OptionDat 2498 +0 PrefData.Set_preftaskMUD
00cc692b +00f cMUD.exe MAIN 18956 +0 TMUDForm.SetTaskVal
00a210f7 +0bb cMUD.exe MultiForm 106 +22 TMultForm.CloseQuery
00c5e8d8 +0b4 cMUD.exe PARENT 10587 +13 TParentForm.DockManagerCloseQuery
0071ad6a +036 cMUD.exe aqDockingBase 7760 +3 TaqCustomDockingManager.DoControlCloseQuery
0071623d +091 cMUD.exe aqDockingBase 5006 +12 TaqCustomDockingControl.DoCloseQuery
00713846 +05e cMUD.exe aqDockingBase 3591 +8 TaqCustomDockingControl.InternalRemoveFromDocking
00713961 +045 cMUD.exe aqDockingBase 3627 +5 TaqCustomDockingControl.RemoveFromDocking
007142a2 +096 cMUD.exe aqDockingBase 3970 +13 TaqCustomDockingControl.DefActionExecuted
0071d3ba +06a cMUD.exe aqDockingBase 9286 +11 TaqCustomDockAction.DoExecute
0071d40a +006 cMUD.exe aqDockingBase 9304 +1 TaqCustomDockAction.Execute
00710a63 +087 cMUD.exe aqDockingBase 2096 +8 TaqDockButton.MouseUp
005066bd +041 cMUD.exe Controls 4831 +2 TControl.DoMouseUp
00506744 +07c cMUD.exe Controls 4843 +8 TControl.WMLButtonUp
00505f8b +1df cMUD.exe Controls 4645 +53 TControl.WndProc
00505c96 +036 cMUD.exe Controls 4552 +5 TControl.Perform
00509b14 +0a8 cMUD.exe Controls 6301 +15 TWinControl.IsControlMouseMsg
00509c20 +0f4 cMUD.exe Controls 6327 +18 TWinControl.WndProc
0050988c +034 cMUD.exe Controls 6237 +3 TWinControl.MainWndProc
0047fef0 +014 cMUD.exe Classes 10966 +8 StdWndProc
77d4bcc7 +00a USER32.dll DispatchMessageA
0052ee40 +0ac cMUD.exe Forms 6873 +13 TApplication.ProcessMessage
0052ee87 +00f cMUD.exe Forms 6892 +1 TApplication.HandleMessage
0052f122 +0a6 cMUD.exe Forms 6976 +16 TApplication.Run
00db7500 +088 cMUD.exe CMUD 344 +18 initialization
7c91312f +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812907 +0b6 kernel32.dll GetVersionExA |
Procedure B hard crash
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#CLOSE untitled" at the command line without quotes
4. Close Session with X button
5. Select File|Open session from the menu
6. Close Sessions Window (ESC)
This procedure also produces a hard crash when step 4 is skipped.
Procedure C produces a no session without causing a crash, seems it might have some timing dependence
1. Launch CMud
2. Close Sessions Window (ESC)
3. Open Package Editor (CTRL-G)
4. Close Session with X button
5. Close Sessions Window (ESC)
6. Close Session with X button |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums
Last edited by Vijilante on Fri Oct 12, 2007 5:15 pm; edited 1 time in total |
 |
|
|
Arde
Enchanter
Joined: 09 Sep 2007
Posts: 605
|
|
_________________
My personal bug|wish list:
-Wrong Priority when copy-paste setting
-1 prompt trigger for Mapper, Session and General Options, not 3 different!
-#SECTION can terminate threads
-Buttons can't start threads |
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Fri Oct 12, 2007 5:19 pm
|
Arde, please look at the list of procedures to replicate the crashes I reported. They are all based off using a fresh launch for every test (lock layout is not set by default). It is likely that your bug was something else having to do with the layout file, and that the 2 different reports are not related even though they are occuring near the same event.
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Oct 12, 2007 6:04 pm
|
Added to bug list for the public version, but I probably won't have these fixed for 2.06 later today.
|
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Fri Oct 12, 2007 6:39 pm
|
I was just screwing around with this some more and it seems the procedures for causing it are even simpler then I thought.
1. Launch CMud
2. Close Sessions Window (ESC)
3. Close untitled session by clicking X
4. Repeat steps 2 and 3 as needed
I got varying hard crashes and no session situations usually by the second closing of the untitled session. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Oct 15, 2007 9:11 pm
|
Confirmed all of these and should have them fixed in 2.07
|
|
|
|
|
|
|
|
