mush stop responding

Posted by Rockeru on Thu 28 Oct 2004 08:24 PM — 9 posts, 31,545 views.

Rockeru Thu 28 Oct 2004 08:24 PM #0

in version 3.50, try to:
rignt clik on info bar, then clik on full screen mode.
ok. it will apperar a new menu "main menu", but when i'll try to clik on it mush stop responding and my 2200+ sempron goes up to 100% usage.
any ideea about?

Flannel USA Thu 28 Oct 2004 09:06 PM #1

Yeah.
Happens for me too nick.
View > Full Screen Mode
"Main Menus" (comes up in full screen mode) never expands, and it freezes.

And rockeru, thats not the info bar (the file edit view etc thing). I think that might be where youre having problems with your plugin too.

Nick Gammon Australia Forum Administrator Sat 30 Oct 2004 07:23 AM #2

I'll check it out.

Nick Gammon Australia Forum Administrator Sun 31 Oct 2004 12:29 AM #3

I tried that on my copy and all that happened was that another menu popped up (a collection of the menus from the normal menu bar). What operating system are you using?

Norry Sun 31 Oct 2004 01:54 AM #4

I'm seeing this too on Windows XP, SP 1; Mushclient 3.50.

Zeno USA Sun 31 Oct 2004 02:51 AM #5

Same here, freezes doing the same thing. Windows XP, SP1. MC 3.50

szAppName : mushclient.exe     szAppVer : 3.5.0.0     szModName : USER32.dll
szModVer : 5.1.2600.0     offset : 00003b8a

Poromenos Greece Sun 31 Oct 2004 08:40 AM #6

Yep, if you right click on the info bar in fullscreen mode and hover over "Main Menus" it freezes, XPSP1.

Nick Gammon Australia Forum Administrator Sun 31 Oct 2004 09:22 PM #7

There is a line in the source code for MUSHclient that is probably responsible:


  while (pWndPopupOwner->GetStyle() & WS_CHILD)
    pWndPopupOwner = pWndPopupOwner->GetParent();

That would go into an infinite loop if each window had the WS_CHILD bit set. Clearly that doesn't happen under earlier versions of Windows. That will need to be fixed in the next version, for now don't do that. :)

Added as bug/suggestion #535.

Nick Gammon Australia Forum Administrator Wed 24 Nov 2004 06:33 AM #8

This rather obscure bug has been fixed in version 3.52.