Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD General Discussion
charneus
Wizard


Joined: 19 Jun 2005
Posts: 1876
Location: California

PostPosted: Sun Jan 20, 2008 8:45 pm   

[2.18] Package editor bug
 
Open up your main session. Then add/open/install a new package.

As usual, it opens the package in it's own tab. Not a problem.

Try deleting that package tab. It deletes your MAIN tab and then proceeds to crash CMUD. At least, that's what it's been doing to me.

For instance, the main tab has all my scripts. I want something from Vijilante's toolbox, but don't want the messy extra tabs (well, not messy, but I don't like extra tabs, personally). I move the stuff from the package to my main, no problem. Then, after I'm finished, I right-click "Vijilante's Toolbox" tab, select "delete tab" and my cursor goes haywire. After a minute or two, my main screen disappears, and CMUD crashes. I've already submitted the bug via the bug report, but I wonder if anyone else experiences this problem.

By the way, no matter what packages I choose to have active, it always... and I mean always put the packages I wish to have deleted in the tabs. They're not even selected as default packages. *sigh*

Charneus
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Tue Jan 22, 2008 10:53 pm   
 
I cannot reproduce this. Exactly how are you deleting the tab? Are you right-clicking and selecting "Delete tab"? When I try this, I even get a warning message about "Do you want to remove package xxx from your session?" and can click Yes/No to confirm the deletion.

So does it only happen after you move stuff from the package? Perhaps you can provide a step-by-step procedure for exactly reproducing the bug that I can try here.

The determination of what a "default package" is comes from your main Preferences/Packages list where you can set which packages are the default packages you want loaded into each new session. If a package is in this list, then it doesn't get a tab in the settings editor unless Show Default Packages view option is on. But if it's not in this default list, then it gets a tab.
Reply with quote
charneus
Wizard


Joined: 19 Jun 2005
Posts: 1876
Location: California

PostPosted: Wed Jan 23, 2008 9:00 am   
 
Ok. Caused it to crash again. Here's step-by-step what I did.

1. Opened my normal session.
2. Opened Package Editor by clicking Settings.
3. File -> Open, chose an installed package.
4. With the new package pane visible, I right-clicked the tab, selected "Delete tab"
5. Prompted with "Remove Package xxx from your session?" - selected "Yes"

Right afterwards, my main session package went *poof* while the new package pane remained visible. After my cursor went haywire, CMUD came up with a crash report. This time, I saved it:

Code:
date/time         : 2008-01-23, 02:51:27, 256ms
computer name     : HOME
user name         : ... <admin>
operating system  : Windows XP Service Pack 2 build 2600
system language   : English
system up time    : 1 day 4 hours
program up time   : 4 minutes 57 seconds
physical memory   : 22/254 MB (free/total)
free disk space   : (D:) 40.99 GB
display mode      : 1024x768, 32 bit
process id        : $7c0
allocated memory  : 69.03 MB
executable        : cMUD.exe
exec. date/time   : 2007-12-14 14:39
version           : 2.18.0.0
madExcept version : 3.0b
contact name      : Charneus
contact email     : ...
callstack crc     : $b0454206, $9adec46b, $9adec46b
exception number  : 1
exception class   : EAccessViolation
exception message : Access violation at address 00C71670 in module 'cMUD.exe'. Read of address 000001BC.

Main ($430):
00c71670 +020 cMUD.exe     SettingFrame     338   +2 TSettingFr.DoSave
00c72825 +019 cMUD.exe     SettingFrame     648   +3 TSettingFr.CloseFrame
00ca7d2c +22c cMUD.exe     MAIN            7044  +43 TMUDForm.FormDestroy
005024c1 +031 cMUD.exe     Forms           2660   +3 TCustomForm.DoDestroy
00502375 +045 cMUD.exe     Forms           2631   +3 TCustomForm.Destroy
00539c5a +012 cMUD.exe     CustomForm        62   +1 TzCustomForm.Destroy
0077add1 +019 cMUD.exe     International     47   +2 TInterForm.Destroy
0077b91a +012 cMUD.exe     zsForm            91   +1 TzForm.Destroy
00a26a62 +012 cMUD.exe     MultiForm        338   +3 TMultForm.Destroy
004e42d0 +0b0 cMUD.exe     Controls        5429  +16 TWinControl.Destroy
004ebc4c +028 cMUD.exe     Controls        8901   +2 TCustomControl.Destroy
00532ab6 +02e cMUD.exe     RzPanel         1423   +5 TRzCustomPanel.Destroy
00722d68 +024 cMUD.exe     zsPanel          268   +3 TzsPanel.Destroy
004e42d0 +0b0 cMUD.exe     Controls        5429  +16 TWinControl.Destroy
004ebc4c +028 cMUD.exe     Controls        8901   +2 TCustomControl.Destroy
00713ba5 +10d cMUD.exe     aqDockingBase   3000  +34 TaqCustomDockingControl.Destroy
00404be0 +008 cMUD.exe     System                    TObject.Free
00481235 +021 cMUD.exe     Contnrs          304   +3 TObjectList.Notify
004707d8 +08c cMUD.exe     Classes         2779   +9 TList.Delete
00470d9a +08e cMUD.exe     Classes         2945   +9 TList.SetCount
00470738 +00c cMUD.exe     Classes         2763   +1 TList.Clear
0071ab65 +005 cMUD.exe     aqDockingBase   6804   +0 TaqCustomDockingManager.ClearMarkedDeletion
0071acf0 +038 cMUD.exe     aqDockingBase   6878   +9 TaqCustomDockingManager.EndUpdate
007150da +0e6 cMUD.exe     aqDockingBase   3614  +22 TaqCustomDockingControl.InternalRemoveFromDocking
0071516d +045 cMUD.exe     aqDockingBase   3636   +5 TaqCustomDockingControl.RemoveFromDocking
00c69264 +050 cMUD.exe     PARENT          8990   +8 TParentForm.RemoveDocking
00c696a1 +111 cMUD.exe     PARENT          9106  +23 TParentForm.CloseWindow
00c617f1 +0c5 cMUD.exe     PARENT          3834  +13 TParentForm.CloseWindow1Click
00c6a501 +011 cMUD.exe     PARENT          9616   +1 TParentForm.WMCloseWindow
004e281f +1df cMUD.exe     Controls        4645  +53 TControl.WndProc
004e654e +18e cMUD.exe     Controls        6342  +33 TWinControl.WndProc
0050362c +478 cMUD.exe     Forms           3098 +103 TCustomForm.WndProc
00ab47af +057 cMUD.exe     cxDBData        1753   +4 TcxDBDataProvider.IsSyncMode
00c012cc +020 cMUD.exe     DXSounds        2013   +9 TCustomDXSound.FormWndProc
00bfea28 +00c cMUD.exe     DXClass          572   +1 TControlSubClass.WndProc
004e6120 +034 cMUD.exe     Controls        6237   +3 TWinControl.MainWndProc
00480398 +014 cMUD.exe     Classes        10966   +8 StdWndProc
7e41f658 +016 USER32.dll                             CallWindowProcA
006d7087 +0a7 cMUD.exe     aqDockingUtils  1728   +7 CallDefWndProc
006d7175 +0dd cMUD.exe     aqDockingUtils  1776  +41 TaqWindowEventFilter.WndProc
00480398 +014 cMUD.exe     Classes        10966   +8 StdWndProc
7e4196c2 +00a USER32.dll                             DispatchMessageA
0050b6d4 +0ac cMUD.exe     Forms           6873  +13 TApplication.ProcessMessage
0050b71b +00f cMUD.exe     Forms           6892   +1 TApplication.HandleMessage
0050b9b6 +0a6 cMUD.exe     Forms           6976  +16 TApplication.Run
00dce84c +088 cMUD.exe     CMUD             344  +18 initialization
7c91312f +069 ntdll.dll                              RtlUnicodeStringToAnsiString
7c812b94 +0b6 kernel32.dll                           GetVersionExA

error details:
Deleting a tab from Package Editor


Hopefully, this will help identify what the bug is, and maybe you'll be able to reproduce it yourself. I'm wondering if it has anything to do with having several settings (over 300 triggers and 160 class folders), but I don't see why that would really cause a problem. If you are unable to reproduce the bug, I can send you my default package to see if that's causing the problem.

Charneus

EDIT: Removed real life info that was probably posted by mistake. - Taz
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Wed Jan 23, 2008 5:40 pm   
 
You'll need to send me your PKG file that you are opening in step (1). I cannot reproduce this in my session.
Reply with quote
charneus
Wizard


Joined: 19 Jun 2005
Posts: 1876
Location: California

PostPosted: Fri Jan 25, 2008 6:14 am   
 
Mailed package to you. Hopefully, that'll help pinpoint the problem.

Charneus
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD General Discussion All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net