Editing Crash

mgag · Post by **mgag** » Fri May 29, 2009 2:58 pm

I am using 3.96s. I am using the Brief keymappings.
Sometimes, when I insert a new line (usually by going to the end of the line and pressing Enter), and press Home, then press the BackSpace key, Zeus will become "Not Responding". I have been trying to make this reproducable, but so far no luck. Its happening about once per day.

Post by **jussij** » Mon Jun 01, 2009 12:18 am

Sometimes, when I insert a new line (usually by going to the end of the line and pressing Enter), and press Home, then press the BackSpace key, Zeus will become "Not Responding". I have been trying to make this reproducable, but so far no luck. Its happening about once per day.

The fact that Zeus is not responding suggests that it is stuck in a loop

What type of file are you editing at the time of the hang

Is is always the same type of file (i.e. document type)

When you hit the backspace key what is the text of the current line and what text is being deleted

The problem could be due to a regexp pattern defintion in the document type, so if you have added any new patterns to the document type I would try removing these.

If it is a pattern defintion issue it will relate to the text that is in the line at the time Zeus hangs.

It could also be related to a bug in the BackspaceSmart function so you could also try binding the backspace key to either the Backspace or BackspaceEx functions.

Its happening about once per day.

Unfortunately I have not seen a similar issue

Cheers Jussi

mgag · Post by **mgag** » Mon Jun 01, 2009 1:34 pm

The document type is C file.
I haven't added any regexp patterns.
Once I allowed Windows to send a crash report - would such a report be helpful to you?

I will be mindful next time of the text pattern.

The problem didn't seem to start happening until a few weeks ago. Or maybe just luck.

Post by **jussij** » Mon Jun 01, 2009 11:49 pm

Once I allowed Windows to send a crash report - would such a report be helpful to you?

When Zeus detects a crash it puts up it's own crash dialog and create a Zeus Err.dmp and ZeusErr.log file.

Since the Zeus crash dialog does not have an option to send the dump automatically you must have seen a Windows crash dialog in which case the crash occurred deep inside Windows itself.

But if you are seeing a Zeus "Not Responding" message from windows then I am pretty sure Zeus has not crashed and as such no crash files will be produced

That is why I said if you are seeing a "Not Responding" message then there is a good chance Zeus is stuck in a loop but because it is in a loop it is not talking to Windows.

If this is what you are seeing you have to make note of the document type you are editing at the time and the text on the line at the time the incident occurs.

With this information you should then be able to replicate the hang at will

Cheers Jussi

Post by **jussij** » Sat Jul 04, 2009 6:59 am

This bug has been fixed in the latest release: http://www.zeusedit.com/forum/viewtopic.php?p=4766

Cheers Jussi