Zugg Software :: View topic

Beginner Joined: 03 Nov 2002 Posts: 27 Location: USA

I've reproduced this on a fresh install of CMUD, so I doubt it has anything to do with the triggers. I've spent quite a while trying to search the forums here and just Google in general with no luck.

Whenever my monitor goes into power-save mode for a length of time (I'm not exactly certain of that length, I just know that it's longer than "a few seconds"), CMUD hangs at 100% CPU usage and I have to kill the task and restart CMUD. Interestingly, this also happens if I'm remoted into my computer (say, using my laptop to remote into my desktop) with fair frequency, though I'm less certain if the power-saving functionality has anything to do with it.

In case it matters, it's a quad-core CPU, so when I say 100%, I mean of one CPU core. Setting the affinity doesn't seem to affect it, in any case.

Posted: Wed May 26, 2010 4:47 pm

Sounds like your system is doing something to power down the networking that isn't working properly. I cannot reproduce this on any of my Windows 7 machines here, so there isn't much I can do about it. CMUD does not support using remote desktop to run it.

Newbie Joined: 27 May 2010 Posts: 1

I am also having a problem with CMUD hanging in Windows 7 - for me it happens after I've locked my workstation for longer than a few minutes - when I come back CMUD will be stuck minimized and I need to force quit the program and restart it.

Posted: Thu May 27, 2010 11:20 pm

Beginner Joined: 03 Nov 2002 Posts: 27 Location: USA

Well, it's not just stuck minimized for me; it's jammed up to 100% CPU (luckily I have a multi-core machine so I can just kill the task without any trouble). It affects, I'm assuming, my system on a more basic level because Windows cannot redraw itself. My taskbar is fine, and I can load/unload software, but I cannot reach the desktop once CMUD locks up; it just stays as whatever the last active screen was (e.g., if I pull up Firefox after CMUD locking, I will still see FF whether I've minimized FF or not, until I load up some other software instead).

I'll definitely keep working on nailing this down if I can. As mentioned, it happens without the Remote Desktop bit going. Everywhere I can possibly find to change a setting, I've already had the computer set to never be allowed to power down a network connection. I have other active network connections that don't go down (such as, for example, SSH connections). Also, I've noticed (now that I'm paying more attention to it) that it sometimes happens during live gameplay. What I have not yet determined is whether or not when I notice it hanging with 100% CPU during active play, it's shortly after returning to the computer from a "break". Is there anything I can do to provide more information (such as getting a memory dump from the Task Manager, or a way to run CMUD in a debug mode)?

This is on Aardwolf, incidentally, and while I do not in any way want to suggest that it's a problem with the mud, they recently re-wrote their telnet stack and I cannot remember whether this occurred prior to that. Nobody else in Aardwolf is complaining about it, and CMUD is reasonably represented amongst the playerbase.

Posted: Fri May 28, 2010 10:36 pm

I actually play Aardwolf myself with CMUD and Windows 7 and don't see this problem either.

Are you using a wireless connection on your laptop? I have a MacBook Pro running Windows that would sometimes lose the wireless connection and it turned out to be an obscure power setting within the wireless driver. I had to go to the Hardware Config, right-click on the Wireless entry and go to Properties, then in the Advanced tab there was a long drop-down list of *lots* of options. One of them was a power-down setting that was getting triggered sometimes.

I doubt this is related to CMUD hanging, but it just reminded me that settings for drivers can be in some rather obscure places in Windows.

About all I can suggest for your problem is to a) find a reliable way to force it to happen, like closing the lid on the laptop to force a standby mode, then b) try turning off various triggers and scripts to see if you can find something that will make the problem go away when disabled. You might also try a completely new connection to the MUD with no settings at all and see if that makes any difference.

If you are running wireless, try a wired network connection. If you are using a wired connection, try wireless. Just keep trying different combinations to learn more about what might cause it.

Sometimes it just ends up being a weird Windows issue. I know that on my MacBook sometimes Windows hangs during the standby process and I have to force a power-off. On my old Toshiba laptop, standby only worked about 50% of the time. Sometimes on my wife's Dell running Vista the screen resolution is all screwed up after returning from standby mode. Laptops and standby mode just seems to be a real problem for Windows.

I just have no idea how CMUD could be doing anything that would interact with the system at that kind of level to cause a hang. CMUD really doesn't do any weird messing around with Windows like zMUD used to, so I don't even know where I would start to look for this kind of problem.

Beginner Joined: 03 Nov 2002 Posts: 27 Location: USA

It's a wired connection, and I'm not entirely sure how it could be the connection dropping when other simultaneous (and more picky about connectivity) apps keep running. I would also be unsure why it would just cause CMUD to peg at 100% CPU, rather than just telling me the connection had failed.

I'm going to try to get to a point where I can reproduce it, but it's not consistent in any way that I can tell. Earlier today Startup->CMUD hanging took about 15 minutes. Just now? It was on for a few hours no issues. I suppose I could try adding the CMUD directory to my AV's Exclusion list and see if that makes any different whatsoever.