Mushclient keeps stalling

I'm having a problem with MUSHclient in which it often stalls, forcing me to reconnect. Noone else has this problem and it works fine on my other client, and mushclient works fine on my other computer, but i'm not sure if they're both setup the same. Any suggestions on how to fix this? Thanks --Miltazar

This is the first report I have had of MUSHclient "stalling" - can you be more specific about what is happening?

Does it just lock up?
Can you use the menu (eg. to exit the program)?
What operating system are you using?
Have you enabled scripting? If so, which language?
Have you written your own scripts?

Have you added any triggers? A trigger like this might cause it to slow down:

Match on: ***** hello there *****

This is because "*" is a wildcard, and multiple wildcards in a row cause the wildcard evaluation to go slowly.

If so, the fix is to make the wildcard a regular expression, and "escape" the asterisk, like this:

Match on: \*\*\*\*\* hello there \*\*\*\*\*

I'm using Windows 95. I don't have any triggers or scripts, what it does is stall up, can use the menus but its like lag, but noone else experiences it and it's fine on another mudclient on the same computer.

Do you mean output stops arriving and never starts again?

So, you can type in commands but when you send them, nothing happens and you don't see the sent command?

Does it happen at the start, after some time (how much time?), does it always happen?

Can you give me the address of the MUD in question, so I can try it?

I have had this same problem Nick.

I am running Windows XP, Mushclient 3.17
I have 1152 megs of ram
1.4GHZ Athlon T-Bird
64Meg Visiontek Xtcy GForce2 Ti

I play at ansalon.wolfpaw.net port 8679
Requires email registration

I log on, and everything is fine, after about 20 minutes my output stops.
I enter commands and they still go through to the mud
I have tested this by being in one room, dropping an item, going a couple rooms away and then reconnecting to get the output back.
I was in a different room and the item I dropped was on the floor where I dropped it.

Sometimes I manage to go for 20 minutes, sometimes 50 minutes.

Sometimes less than a minute
Its always different, but the output stops and i can no longer see new lines. yet i am still online and sending info to the mud.

I have talked to my ISP, Theyclaim there is no issue with my computer's connection.

Its either an issue with MushClient, or with the server at ansalon. I don't know.

I am not sure if it is the same thing or not, but I have had occations where the mud server I log into has suffered a momentary problem and I can recieve text, but nothing goes the other way. Something about the way Mushclient interracts with windows may be causing it, but I haven't a clue what it would be.

A similar glitch is the fact that if a router dies someplace mushclient will try to send your commands, but then when the router comes back online mushclient will say that the remote server disconnected you. If you know that something has lagged though and you leave it alone, then when router starts working again mushclient will stay connected.

Both of these things seem to be the reverse of what they are talking about, though possibly related. It is probably windows doing it combined with something mushclient does that other clients don't/can't. Problem is that the list may be pretty long in that regards. ;) lol

I don't get disconnected.
If I leave it alone it will just stay stalled untill I ctrl+shift+k

If I idle too long the server will disconnect me because of anti-idle progs

Other than that i staycnonected as if nothing is wrong
Its not a router dying either, I have tracert'd and ping'd when it has happened, and those have turned up fine

MUSHclient uses Windows "messages" to let it know when incoming text has arrived, because of the asynchronous nature of TCP/IP connections. Thus if it doesn't get the message it won't react.

However sending text would still work because that is a different message (keyboard presses, for example).

This is happening rarely, but obviously occasionally. I think it happened to me once, but went away after closing the world or MUSHclient.

The only thing I can suggest is upgrading your Winsock (Windows Sockets) DLL, if that is possible.

As for the disconnections, if a router is down, MUSHclient will only notice if it attempts to send a packet, so if the router goes down, and up again, and there is no activity in the meantime, the world will stay connected. If you send while the network (router or whatever) is down, then it notices that the packet doesn't get a response and disconnects you.

I figured my glitch could be that, but the client only seems to 'notice' this if the other end starts sending again. I am pretty sure that I have not had it disconnect on me when a send was pending until 'after' the problem clears up. However trying to disconnect and reconnect, or if an extremely long delay occures when nothing is pending, it will disconnect normally. Kind of odd.

Also, doesn't surprise me that the other problem is likely Winbloze winsock related. ;)

I was checking winsock out.. it seems that the winsock.dll for my OS which is XP Pro. I have that version already

If I close out the world, or MC thats fine, but it happens everytime I open this world... closing out the world, and or MC down't help

Ok well... This is totally sucking...

According the the dll help desk online at MS.com, I have the right version, it says nothing about an updated version.

Not only that, I can not find a Dl link for Winsock.dll to begin with anyways...

If anyone has a clue about where I may find this, please lemme know, I am so tired of having to disconnect and reconnect ever 5-20 minutes

This is one of the frustrations of writing software. I have over a thousand registered users, and probably another 10,000 unregistered ones.

About 3 of those report this problem. Clearly it is not happening to everyone, and as for me, I have MUSHclient running for 10 days without any such problem.

Thus, it is likely to be something environmental, like the operating system or its DLLs.

I'm sorry, since I can't reproduce the problem I can't really fix it. I don't want to make changes willy nilly to a program that is otherwise working, and in any case, wouldn't know where to start, since it works for 99% of the users.

Version 3.43 has extra code in it that should stop this "stalling" issue.

I'm having the same issue. If I don't type into the MUCK, the output stops updating, and I get no message. If I type again, say 15 minutes later, I will get all the backlog, which could include being kicked off for inactivity.. I'll check 3.43 tho

Sounds like the MUCK. My server that my MUD is currently hosted on, does that. The server lags, and MC disconnects then reconnects instantly. Using the newest version, but its not a problem with MC, at least not with my problem.

This is an old topic. Try the latest version of MUSHclient. I haven't had this report on recent versions.

Heya Nick,

I'm using the latest version (3.50) of MUSHclient and I also get the send " Lag " problem. I still see what's going on in the room most of the time, and if I try to enter text or a command, I can see the ZoneAlarm bar flashing, and the activity lights on my switch and router flash. Yet, nothing appears on the MU*.

I some how doubt this is purely a MUSHclient problem, because if I try to open FireFox, I get no response when trying to load a web page. After a few to several minutes, the page loads and if I switch back to the MUSHclient window, the backlog of "spam" fills the screen. MUSHclient might some how be "lighting the fuse" for the problem to start.

I have noticed on a few occasions that when I start MUSHclient and try to connect to a world, I get a message that it's unable to connect because the buffer is full. Usually re-booting the computer cures it and I can connect as normal.

I'm using Windoze XP-Pro, with Service Pack 2 installed and all applicable updates. The problem existed even before I did the SP2 upgrade.

Have a good one,
Haflinger