Zugg Software :: View topic - [1.23] Infinite loop importing *.MUD file after #CAPTURE

Wizard Joined: 14 Aug 2004 Posts: 1269

On zMUD, I had a few capture windows. There were initially created via the #CAPTURE command and I did nothing else with them - no settings, just possibly a change of one of the colours - not sure.

1. So in every version of CMUD that I test I copy my zMUD settings to my CMUD folder, either copy my mudchar.db and get CMUD to import it or create a new session and import my main *.MUD file that way. (It doesn't matter which.)

2. This time, like usual, I decided to run the compatibility report to compile all my settings.

2a. I click on one of the settings and the Package Editor opens. I do a search but don't make any changes.

3. Then I logged into the MUD to do some proper testing.

4. There is a 'narrate', which I capture to a Narrates window. A converting dialog comes up with a progress bar, but when the progress reaches 100%, it starts again from the beginning. This keeps happening and CMUD uses 100% CPU while this is going on.

5. Eventually CMUD detects that is an infinite loop and asks if I want to disable the trigger. I say yes.

6. The same infinite loop message comes up instantly one more time and I say yes again.

7. About 50 or 100 copies of the same narrate line get echoes to my _main_ mud screen.

8. I try to alt-tab to IE and get the Package Editor instead. I notice that the package Editor is showing dozens of copies of "Narrates" _and_ "Narrates.mud", in addition to "Main.mud" (greyed out) in the list of packages to load for this session. I also notice that currently loaded in the left-hand tree view is my main mud file, let's call it Main.mud, Narrates, and Narrates.mud.

9. I take a screenshot. How do I upload that?

10. I click on the X to close CMUD.

11. The CMUD window closes and then a browse dialog comes up entitled 'Save package "Narrates" as'.

12. I enter 'Narrates.pkg' and press Save. The window closes, but if I do alt-tab, I notice it's actually still there, so it must have popped up again. I see that 'Narrates.pkg' is now listed as a file.

13. I press Save again. I am not asked if I want to overwrite an existing file.

14. I try again and again and it keeps coming back. (I take a screenshot.)

15. I press the Show Desktop button (minimise all).

16. I alt-tab back to the Save package window.

17. I click save again and now I can see the window disappearing for 1-3 seconds and then reappearing. I repeat this about 20 or 30 times.

18. Finally I go into Task Manager and End Task on the CMUD Application. The disk makes a sound and it disappears off the Applications tab. The Save package window is still showing though. [EDIT: I'm pretty sure I actually closed zMUD here (didn't look closely enough).]

19. I open the Processes tab and see 4 CMUD processes. I only open 1 CMUD instance, but I know there are usually two when everything is normal. Two of them don't use much memory, 1 uses about 22 MB, and one uses about 70 MB. [Edit: I'm sure these all were CMUD - zMUD had already closed above, and all 4 processes were listed next to each other.]

20. I decide to End Process on the 22 MB one. Two processes disappear, but the 70 MB one and one small remains. The Save package window remains too.

21. I kill the 70 MB one. The Save package window finally disappears.

---------

This has been a problem on (all?) previous versions of CMUD - I have reported it before once via the Send Feedback menu option when I was at step 4, and once when I got an Access Violation. We had some correspondance on the latter one:
The last of which was sent on 13-Oct-06 at 7:33 PM BST with subject: Re: Bug Report: CMUD - Access violation at address 004033E1 in module 'cMUD.exe'. Read of address 043B6B58. {15873}
I sent you the trigger pattern, the script, and the mud file a couple of minutes earlier.

EDIT history:
1. I added some to step 8 after looking at the screendump.
2. But a couple of edits in 18 and 19 (marked).

Wizard Joined: 14 Aug 2004 Posts: 1269

I reopened CMUD to try and replicate the problem. _This_ time, when I got a tell (also captured with #CAPTURE), I got the converting progress bar only once or twice - no infinite loop. However two new windows appeared. "Tells.mud" and "Tells". When the first narrate happened, two more windows appeared: "Narrates.mud" and "Narrates".

However, on closing CMUD I still get the Saving package window. This time I decided to press Cancel. I had to press Cancel four times I think before it went away. (I think I tried Cancel back in October and it didn't seem to help, but maybe, due to the infinite loop, I would have needed to press cancel some 100 times or something.)

Hope this helps.

Posted: Fri Dec 15, 2006 12:16 am

Wizard Joined: 14 Aug 2004 Posts: 1269

Oh, also, I discovered that the copy of Narrates.pkg that got saved in step 12 is in my CMUD 1.22 folder and not my CMUD 1.23 folder. I don't know why it got saved there (I didn't change the default location). I double-checked my Sessions and they are set to use my CMUD 1.23 folder...

Posted: Fri Dec 15, 2006 2:15 am

Yes, it will also load a *.PKG file with the same name as the window. This is also something I have removed from 1.24. Definitely makes the capture windows more complicated and annoying than they should be. Having the #capture command just create a new window within the same package and setting your preferences for that window just like any other window is definitely the better way to go.

So thanks for reporting this problem...it was something old from the early beta versions that got left around messing stuff up :)

Posted: Fri Dec 15, 2006 1:55 pm

So that is what Cmud has been doing. Definitely give 1.24 a try when I get home. The whole deal with windows had about turned me off to using Cmud.