Accidental zoom triggers crash

[James3359]

i have found from time to time a crash occurs without warning, and I am finding it hard to give exact steps to reproduce it. As far as I can tell Crash Reporter is not generating anything, but I am getting something in Console in User Diagnostic Reports.

As far as I can tell the crash happens when I have three or more documents open, some or all of which have unsaved material in them, and some of which will be Word documents opened from within emails. From time to time I accidentally trigger the command-two-finger zoom (as mentioned here by Lorinda). Usually it is a zoom one way, quickly corrected by zooming back again.

The document I am working on flashes up and down in size, the multicolour beach ball appears and spins for a couple of seconds and NeoOffice and all its windows disappear.

Typically NeoOffice will not then relaunch the first time I click it on the dock, a second click is required to persuade it to launch.

So far, there has only been one occasion on which I have suffered data loss, and that only minor. Most times the recovery process puts me back to where I was, even including unsaved changes.

I'm sorry not to be able to post an absolutely reliable way of triggering this crash, and I'm open to suggestions about what I might try in order to identify that. I realise that without a reliable way of generating the crash it may not be possible to identify what is causing it in order to try and fix it.

I attach the User Diagnostic report in case it is of help.

[pluby]

[James3359]

Looking at Console, I have a number of these User Diagnostics which are, I think, associated with the crash. There was one yesterday, and before that a gap of ten or twelve days prior to which there was a rash of several crashes over a few days.

The short answer is that I think I am likely to generate a crash again, especially if I don't make an effort to avoid it (i.e. if I open lots of documents, do lots of editing and don't save frequently enough).

It is likely that I won't be using NO intensively for nearly a week from 31st March, so this may affect what priority you want to give to posting a test patch.

[pluby]

[James3359]

I'm sorry that I'm not completely sure. It is more likely, I think, that it is the pinch gesture - but I'm not sure

[pluby]

OK. Below is a debug patch:

Intel:
http://juliette.neooffice.org/test/NeoOffice-3.3-Patch-5-Test-5-Debug-1-Intel.dmg

To capture the messages that this debug patch will generate, can you run NeoOffice using the following steps?:

1. Quit NeoOffice if it is running.

2. Launch the /Applications/Utilities/Terminal application, paste the following command into the Terminal window, and press the Return key. This will launch NeoOffice and cause the debug messages to be output to the Terminal window:

[James3359]

OK, I've provoked the crash. It is a pinch gesture, I think, accidentally generated by my lazy thumbs trailing across the trackpad. I attach the Terminal Screenshot and the User Diagnostic Report log.

I hope this is of some help. Please let me know if I can do anuything else useful. In the meantime I am installing the non-debug patch.

Best wishes

James

[pluby]

Thank you for the output. I have updated a new debug test patch that will hopefully print out more messages and cause your next crash log to have more detail.

Can you install the following debug patch and repeat the same steps in my last post?:

Intel:
http://juliette.neooffice.org/test/NeoOffice-3.3-Patch-5-Test-5-Debug-2-Intel.dmg

Like before, once you get a crash you can reinstall the regular test patch in step 5 in my last post.

Patrick

[James3359]

I've had a go, but can't seem to make it crash ATM. I need to do other things now, but will try and give it another go in the next couple of days.

[pluby]

[James3359]

I've had another go at trying to provoke a crash, and will do the same again in a minute. NO got into an odd state where one of the numerous windows that I had opened stayed the front and would neither minimise or close. Other windows that were partly visible behind it could be brought forward, in relation to each other, by clicking on them, but this window remained at the front. It would allow input and editing. I did follow the procedure used to get a sample if NeoOffice hangs (although it wasn't quite a classic hang as I could still perform some operations on the frontmost window). I will happily attach that if you think it is useful. But I'm a bit wary of adding what might be another different issue to the list.

James

[pluby]

Go ahead and post the sample. Was the problem window a regular document window? Or was it a floating tool window or a dialog window?

Patrick

[James3359]

Sample posted.

It was a regular document window.

[pluby]

Your sample shows that NeoOffice was starting a print job. That would explain why one document window was being pushed to the front and you could not close or minimize it.

Did you press the Print toolbar icon or select the File :: Print menu right before this behavior occured? If so, did you see the native print dialog attached to any of the other windows? Normally, the print dialog will be attached to the currently active window which may not be the document window that you are printing.

Patrick

[pluby]