 |
Martaigne
Wanderer
Joined: 05 Jan 2002
Posts: 88
Location: Atlanta, GA
|
 Posted: Mon Jun 21, 2010 5:11 am
[3.20] Closing one session tab while multiple sessions are open crashes CMUD
|
I had one session open in offline mode, which does have a lot of code in it, and had an empty session open in another tab. I close the first tab, and boom!
| Code: |
date/time : 2010-06-21, 01:06:14, 915ms
computer name : PHOENIX
user name : Chris <admin>
registered owner : Chris ******
operating system : Windows XP Service Pack 3 build 2600
system language : English
system up time : 30 days 8 hours
program up time : 31 seconds
processors : 2x Pentium(R) Dual-Core CPU E5400 @ 2.70GHz
physical memory : 2381/3327 MB (free/total)
free disk space : (C:) 70.52 GB
display mode : 1366x768, 32 bit
process id : $13e4
allocated memory : 30.05 MB
executable : cMUD.exe
exec. date/time : 2010-06-18 17:00
version : 3.20.0.0
compiled with : BCB 2006/07
madExcept version : 3.0k
contact name : Chris
contact email : *****************
callstack crc : $30f4c55c, $e3533e80, $e3533e80
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 007323B1 in module 'cMUD.exe'. Read of address 00000000. |
| Code: |
Main ($14dc):
007323b1 +15 cMUD.exe aqDocking 3406 +2 TaqInsideContainer.ResetTabControl
00730dec +b0 cMUD.exe aqDocking 2727 +10 TaqInsideContainer.DeleteChild
00741072 +2a cMUD.exe aqDockingBase 3216 +6 TaqCustomDockingControl.SetParentItem
00741dc4 +40 cMUD.exe aqDockingBase 3586 +8 TaqCustomDockingControl.HideControl
00741f99 +e9 cMUD.exe aqDockingBase 3646 +25 TaqCustomDockingControl.InternalRemoveFromDocking
0074626e +92 cMUD.exe aqDockingBase 6074 +9 TaqCustomDockingContainer.Destroy
0072f93c +68 cMUD.exe aqDocking 2067 +10 TaqInsideContainer.Destroy
00404dcc +08 cMUD.exe System 16515 +0 TObject.Free
00740b60 +00 cMUD.exe aqDockingBase 3067 +0 TaqCustomDockingControl.Release
00746869 +09 cMUD.exe aqDockingBase 6278 +2 TaqCustomDockingContainer.Release
00c9ea5d +75 cMUD.exe PARENT 10463 +9 TParentForm.HideWindowHandler
0074bf76 +4e cMUD.exe aqDockingBase 9531 +8 TaqCustomDockAction.DoExecute
0074bfeb +0f cMUD.exe aqDockingBase 9552 +1 TaqCustomDockAction.Execute
0074c362 +1e cMUD.exe aqDockingBase 9700 +3 TaqDockMenuItem.Click
004b28cf +13 cMUD.exe Menus TMenu.DispatchCommand
004b38d6 +82 cMUD.exe Menus TPopupList.WndProc
004b3825 +1d cMUD.exe Menus TPopupList.MainWndProc
0047d424 +14 cMUD.exe Classes StdWndProc
7e4196c2 +0a USER32.dll DispatchMessageA
004aa76c +fc cMUD.exe Forms TApplication.ProcessMessage
004aa7a6 +0a cMUD.exe Forms TApplication.HandleMessage
004aaa9b +b3 cMUD.exe Forms TApplication.Run
00e45b4c +88 cMUD.exe CMUD 373 +20 initialization
7c912c21 +69 ntdll.dll RtlUnicodeStringToAnsiString |
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Jun 21, 2010 4:59 pm
|
I could not reproduce this. Can you come up with a procedure to test this starting from a blank session window?
The crash looks more like something was corrupted in your window layout file. |
|
|
|
|
Martaigne
Wanderer
Joined: 05 Jan 2002
Posts: 88
Location: Atlanta, GA
|
Posted: Mon Jun 21, 2010 5:22 pm
|
Hm, no. I don't know what could be corrupted since I just blew away CMUD entirely to install 3.20, and imported my session XML to a new session.
I can reproduce this with no problems by right-clicking the tab group for my session and selecting 'close'. It doesn't do the same thing for blank sessions. If I don't have another session open, I can close that session with no issues.
I'll keep playing with it to see if I can figure something consistent out. |
|
|
|
|
|
|
|
