Hi,
I've been having Mushclient crash on me (windows "has stopped working" error) randomly while playing, and am not sure how to trace the cause of error.
I'm currently running Mushclient 4.77, but have had these crashes in earlier versions. The strangest thing is that they /only/ happen on my windows 7 laptop, and never on my windows XP desktop. I run Mushclient from dropbox, a free cloud data hosting service, so the scripts and program should be identical on both win 7/XP.
I would suspect it's the result of some script malfunction, since the crashes only happen when I'm actively playing. They have happened while I was doing completely different things, eg entering a speedwalk alias, walking manually, or killing a mob. However, I cannot reproduce the crashes reliably, nor are they frequent (once in a several hours, sometimes no issues for days. Also, even if I repeat the exact same action again, it usually works [or will in one or two tries]).
I understand that what I know is pretty much useless in identifying what's the problem, so I'm asking if there's anything I can do that would let me try to isolate the cause, or if there's any way to get more information the next time it crashes?
Thanks for any help!
I've been having Mushclient crash on me (windows "has stopped working" error) randomly while playing, and am not sure how to trace the cause of error.
I'm currently running Mushclient 4.77, but have had these crashes in earlier versions. The strangest thing is that they /only/ happen on my windows 7 laptop, and never on my windows XP desktop. I run Mushclient from dropbox, a free cloud data hosting service, so the scripts and program should be identical on both win 7/XP.
I would suspect it's the result of some script malfunction, since the crashes only happen when I'm actively playing. They have happened while I was doing completely different things, eg entering a speedwalk alias, walking manually, or killing a mob. However, I cannot reproduce the crashes reliably, nor are they frequent (once in a several hours, sometimes no issues for days. Also, even if I repeat the exact same action again, it usually works [or will in one or two tries]).
I understand that what I know is pretty much useless in identifying what's the problem, so I'm asking if there's anything I can do that would let me try to isolate the cause, or if there's any way to get more information the next time it crashes?
Thanks for any help!