Zugg Software :: View topic - [2.35] CMUD crashes while loading a package (was: tired of losing my work)

Enchanter Joined: 09 Sep 2007 Posts: 605

I had CMUD crash today. I was adding some new scripts to my package for several hours, restart CMUD later, but it failed to load my package. Evil or Very Mad

Accidentally, I've made an XML file of my settings while I work on my scripts so I managed to restore some code, but scripts for the last 2 hours of my work are gone.

I want to ask for XML auto-export option at closing a session. Will it be 2.XX or 3.XX version - I don't care. It seems that text files of any kind is the best way to secure my work. Backup of session package file is useless as it always get corrupted along with main package file. Why CMUD ever creates it then? Let's add something that *really* can help. With auto-export option enabled, CMUD could create an xml file of session package when user about to close his/her session. The algorithm is quite simple and will not be hard to implement: 1) Copy existing package.xml to package.xml.bak and 2) Export current session to package.xml. This should be enough to recreate package in any situation without losing anything.

===========================

Enchanter Joined: 09 Sep 2007 Posts: 605

Nice. There are no obvious errors in last exported XML file, but CMUD can't recreate session from it. Evil or Very Mad

Interestingly, every time I trying create a package from XML file, I'm getting an Access Violation error at a different point.

Enchanter Joined: 09 Sep 2007 Posts: 605

Further testing: last XML file that CMUD accepts for import was made by CMUD 2.30. I don't have XMLs from 2.31 and 2.32, but CMUD crashes while trying to import both files from 2.33 and 2.34. If copy exported settings manually and paste them to the XML tab of the Package Editor, then it says that there is invalid data after valid xml document (at the point specified in error message, near the end of file, there is an end of settings for main window and start of settings for child windows).
Now, there is no differences at first glance between files outline from 2.30 and 2.33, so something should be messed up elsewhere.

UPDATE: There is another thread on troubles with XML import, I leave this thread for my initial request only.

Posted: Tue Aug 05, 2008 5:59 am

If CMUD is failing to load *any* package, please email it to me at sales@zuggsoft.com as that should be impossible. I have no plans for an "auto export" feature because CMUD is supposed to be saving your changes automatically in your package and I'd rather spend my time getting that to work as it should rather than adding an extra feature that isn't needed.

I don't have all of my test files with me here at the con, but I did some basic export/import and haven't been able to reproduce the problems. But hopefully people will send me the XML files that are having problems to my email for when I get back next week.

Wizard Joined: 14 Aug 2004 Posts: 1269

I suspect it may involve XML that contains button definitions, because that's where some the of XML changes were...

Enchanter Joined: 09 Sep 2007 Posts: 605

Very well then... Today I've tried to make more testing and run into some interesting results. First of all, I was able to load my package via File\Open command of the Package Editor. I'm still can't load it as main session package (CMUD gives AV crash immediately), I can open it only in addition to already opened session package. Next, when I load my package in the PE, it shows up with all but main window closed. If I tickle child windows visibility checkboxes, CMUD crashes on saving changes. Then, after CMUD restart, I'm getting exactly the same AV crash at the same address as I mentioned in the first post in this thread.
Phew, at least I've got all my scripts back, safe in the XML file. Confused

And, btw, I sent my package and offending XML file from CMUD 2.34 to sales.

Posted: Tue Aug 05, 2008 4:33 pm

If you can load it via File/Open but not from the session screen, then try holding down the SHIFT key when you use "Open Offline" to let CMUD reset the layout file. It sounds like maybe the window layout is messed up and that might be causing a crash, especially since you mentioned that messing with the visibility checkboxes causes problems.

Enchanter Joined: 09 Sep 2007 Posts: 605

No, it didn't help. I know that errors in the window layout file sometimes can cause troubles with session loading and actually have tried layout reset yesterday.

Update: I ran a quick test 5 minutes ago: in a completely new test session I opened the PE, add my package and close CMUD without changing anything. After CMUD restart I got AV on session load. Close CMUD, delete .xly and .tbz files, start CMUD, load session - the same AV, at the same address while trying to read the same address as I wrote in the first post. Seems that windows visibility has nothing common to things happening.

Enchanter Joined: 09 Sep 2007 Posts: 605

Zugg, have you receive my package and xml file I sent you to sales?

Posted: Tue Aug 12, 2008 4:29 pm

Nope, I haven't seen anything from you Arde. Try sending them again and make sure CMUD is in your subject line.

Enchanter Joined: 09 Sep 2007 Posts: 605

*sigh* Sent again. With CMUD in the subject line.

Posted: Tue Aug 12, 2008 7:57 pm

OK, still no email received here. And I'm not seeing anything in my mail logs or spam filter reports. How are you sending the files and what email program are you using? Are the files within some sort of archive?

Enchanter Joined: 09 Sep 2007 Posts: 605

Ok, I think that is wolfpaw again rejects domain name. I'll try now to send you files from another mail account.

Update: ...sent. Have you got my message?

Posted: Tue Aug 12, 2008 9:51 pm

Hmm, still nothing. Man I'm really getting tired of these email issues. As I said, What email program are you using? Also, I already asked whether you are sending the files within any sort of archive file or not.

Wolfpaw shouldn't be rejecting your domain name. Like I said, I don't even see anything in the log file. So it's almost like your email system isn't even sending it somehow. Or maybe the attachment is too large and your ISP is rejecting it?

Is there anywhere you can post the files for me to download?

Spam has completely ruined the world!!!

Enchanter Joined: 09 Sep 2007 Posts: 605

I sent files from "The Bat!" e-mail program, as well as from the a web mail service. Files were not within any archive.
Ok, I've uploaded files, check your PM

Update: mail servers at both accounts accepts at least 10 MB attachments, maybe more, and web mail offers 750 MB attachments (although I dunno who can receive it) - not any problems with sending 200Kb attachment from my side.

Posted: Tue Aug 12, 2008 10:31 pm

Got the files. And I can confirm that I can load your package manually in the settings editor but when loaded as part of a session I get the crash. So I should be able to fix that. I also get a crash when I try to import the XML, so I'll look at that too.

Still don't know what the problem was with the email. I've seen trouble with Bat! before, but the web mail service should have worked.

Posted: Wed Aug 13, 2008 8:39 pm

I found the cause of your crash when opening your package:

You have an event called OnTrace. This event gets called from within a function that is used to display text on the status bar. So when CMUD first loads and tries to display the status bar, your event fires, which creates a new window to display your trace info. But at this early point in CMUD, you can't create windows...CMUD doesn't expect status bar text to have side effects like this.

Not sure if I can handle this or not...I'll probably need to disable events when displaying status bar text. As a workaround you should disable your onTrace event and only enable it once your session is loaded.

Enchanter Joined: 09 Sep 2007 Posts: 605

Hm... Yes, I've add tracing event call to that function long time ago, but all that time I had tracing flag set to 0 (off). Before crash happened I've raised flag to debug that @createEditLink function and after closing CMUD this definitely could trigger the problem.

Could CMUD display status window closer to the end of loading sequence? I can disable tracing event, but I then I must disable error reporting event as well, which uses the same window as onTrace event handler...

Posted: Wed Aug 13, 2008 9:41 pm

OK, I fixed this problem. The underlying problem was that the onTrace event was calling #WINDOW to display stuff to a window, which was causing the window to be created because CMUD was already in the middle of creating the windows. What I have done is to prevent the #WINDOW routine from creating a new window while CMUD is in the middle of creating other windows. This should prevent the loop that was causing the crash without messing with events.

I also found the problem with the XML Import of the file you sent me. The problem in this case was a bit more common. When windows were being docked to other windows and the "Dock relative to" field in the Window properties was set, the XML was exporting the database ID value of the window being docked with. But when importing XML into a new package database, the ID values of settings can change. So now it was referencing a different setting instead of the window.

I have added error checking so that importing existing files with this problem won't crash, but they will still lose the Dock Relative To window property. To fix this, I have change the XML Export to save the unique UID of the window being docked to instead of the database ID field. This will prevent this property from being lost across an export/import when the ID values have changed.

Enchanter Joined: 09 Sep 2007 Posts: 605

In other words, in 2.36 I'll be able to load my package that caused crash in 2.35? Excellent!

Enchanter Joined: 09 Sep 2007 Posts: 605

I've load my 2.35 package successfully, yay! Very Happy

Posted: Fri Aug 15, 2008 5:02 pm

No, it shouldn't abort the function call or event at all. It only prevents the #WINDOW command from running. The rest of the script should be unaffected.

Enchanter Joined: 09 Sep 2007 Posts: 605

Then it is strange. If CMUD have prevented the #WINDOW from running while loading, then status window gets messed up. Any changes in it after CMUD completely loads a session restores its normal view.