Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - NeoOffice Crashes After Inserting Updating Date Field
NeoOffice Crashes After Inserting Updating Date Field
 
   NeoOffice Forum Index -> NeoOffice Releases
View previous topic :: View next topic  
Author Message
GridLox
Captain


Joined: May 02, 2009
Posts: 51
Location: Adelaide, South Australia

PostPosted: Thu Apr 21, 2011 7:29 pm    Post subject: NeoOffice Crashes After Inserting Updating Date Field

Hello Patrick and gang. Have recently downloaded and installed NO 3.2, and found a bug (which may of course have been in previous iterations).

After inserting an updating Date Field (Writer), I clicked on Help and NO immediately crashed. After trying various sequences, it appears to specifically be associated with the field insertion.

Crash log attached.
Evil or Very Mad … no, not really, more … Confused

P.S. I thought I attached the crash log file, but couldn't see it in Preview?!

_________________
"His hands were pure; but he had no hands"
Charles Peguy about Immanuel Kant.
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Thu Apr 21, 2011 7:54 pm    Post subject:

I am not able to reproduce the crash that you see. Below are the steps that I used in a new, empty Writer document. Do I need to use different steps? Also, does it only occur in a specific document of yours?:

1. Open new Writer document
2. Select the Insert :: Fields :: Date menu
3. Select the Help :: NeoOffice Help menu -or- double-click on the date field and press the Help button in the dialog that appears

Patrick
Back to top
GridLox
Captain


Joined: May 02, 2009
Posts: 51
Location: Adelaide, South Australia

PostPosted: Fri Apr 22, 2011 5:05 pm    Post subject:

OK. It seems the problem arises when the 'automatic update date' condition is selected at the outset - by proceeding:
1. Open new Writer document
2. Select the Insert :: Fields :: [color=red]Other[/color] menu
3. Select the Help :: NeoOffice Help menu -or- double-click on the date field and press the Help button in the dialog that appears
[i]See CrashLog_23/04/2011_A[/i]
OR
1. Open new Writer document
2. Select the Insert :: Fields :: Date menu
3. Select (highlight) resulting date entry in document - i.e. double-click on the date field; select "Date" in the "Select" (middle) list - NOT "Date (Fixed)".
4. Select the Help :: NeoOffice Help menu -or- double-click on the date field and press the Help button in the dialog that appears
[i]See CrashLog_23/04/2011_B[/i]

_________________
"His hands were pure; but he had no hands"
Charles Peguy about Immanuel Kant.
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Fri Apr 22, 2011 6:05 pm    Post subject:

Thank you for steps. Unfortunately, I still cannot reproduce the crashing on my Mac OS X 10.5.8 Intel machine.

I was hoping that I could see your crash logs but it looks like attaching them failed for you. In the "Add an Attachment" section when you create a post, are you pressing the "Add Attachment" button after you select a file using the "Browse" button?

If you can try attaching your crash logs again, my hope is that the crash logs will give me some ideas of where to look next for the cause of the crash that you are seeing.

Patrick
Back to top
grahamperrin
Sentinel


Joined: Oct 08, 2004
Posts: 23
Location: Brighton and Hove, United Kingdom

PostPosted: Sat Apr 23, 2011 4:10 am    Post subject:

GridLox wrote:

1. Open new Writer document
2. Select the Insert :: Fields :: Date menu
3. …

4. … -or- double-click on the date field and press the Help button in the dialog that appears


I can't reproduce a crash with those actions.
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sun Apr 24, 2011 3:48 pm    Post subject:

pluby wrote:
If you can try attaching your crash logs again, my hope is that the crash logs will give me some ideas of where to look next for the cause of the crash that you are seeing.


FYI. My current working theory is that this crash only occurs when some unknown NeoOffice preferences have been set. So once you are able to attach a crash log successfully, I will likely have you attach your NeoOffice user preferences folder.

Patrick
Back to top
GridLox
Captain


Joined: May 02, 2009
Posts: 51
Location: Adelaide, South Australia

PostPosted: Mon Apr 25, 2011 12:57 am    Post subject:

OK. Today the crash occurred whenever I clicked on the "Help" button in the Menu Bar (top of screen).

I shall first attempt to succeed in attaching a crash log file … ahuh! … doesn't like "/"s in filename - remove same.

Now let's see how we go.

_________________
"His hands were pure; but he had no hands"
Charles Peguy about Immanuel Kant.
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Mon Apr 25, 2011 8:16 am    Post subject:

Thank you for the crash log. The good news is that I have seen this same crash log before in this forum topic. The bad news is I am still perplexed as to what is causing this crash.

The summarize what we know so far about this crash, the crash is occurring in Mac OS X's "draw the menu in the menubar that the user clicked on". My theory is that the crash occurs because Apple's Java code is changing the state of the menu after the click and just before the draw.

What perplexes me is that in NeoOffice 3.2 we are using the same Java code to create menus in the menubar as NeoOffice 3.1.2 so I suspect that some other change in our code is indirectly triggering this.

Today I will investigate all changes in the NeoOffice code that might affect menus. In the meantime, can you tell us if you remember any of the following occurring when these crashes happen?:

1. You have any floating windows open. If so, can you tell us which floating windows?

2. You had just changed the active document?

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Mon Apr 25, 2011 9:40 am    Post subject:

I think that I might have found the trigger for this crashing bug. In NeoOffice 3.1.2, we used Apple's older, deprecated Carbon menu tracking event handling functions. These functions did forced NeoOffice's underlying OpenOffice.org code to update NeoOffice's menus when you first click on the menubar.

In NeoOffice 3.2, we switched to Apple's newer Cocoa functions to know when you first click on the menubar. As a result of this switch, it appears that we are forcing the OpenOffice.org code to update the menus slightly later in the Apple's menu display process.

I have changed the NeoOffice 3.2 code to move as much of the OpenOffice.org code menu updating code earlier in the menu display process in the following test patch. Can you install the following test patch and tell us if the crashing reoccurs? If so, can you post a new crash log in case the location of the crash has changed as a result of my fix?:

Intel:
http://joe.neooffice.org/test/NeoOffice-3.2-Patch-0-Test-1-Intel.dmg

Patrick
Back to top
GridLox
Captain


Joined: May 02, 2009
Posts: 51
Location: Adelaide, South Australia

PostPosted: Mon Apr 25, 2011 9:56 pm    Post subject:

When I attempted to access the patch, I get a message saying "Sorry, you requested a file that can only be downloaded to a Mac OS X machine and your web browser does not appear to be running on a Mac OS X machine." … then defaulted to NO 3.2. This occurred when using both Chrome and Safari. (iMac4,1; Intel Core Duo; 1.83 GHz; with 2 GB RAM, running OS X 10.6.Cool
_________________
"His hands were pure; but he had no hands"
Charles Peguy about Immanuel Kant.
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Mon Apr 25, 2011 10:03 pm    Post subject:

GridLox wrote:
When I attempted to access the patch, I get a message saying "Sorry, you requested a file that can only be downloaded to a Mac OS X machine and your web browser does not appear to be running on a Mac OS X machine." … then defaulted to NO 3.2. This occurred when using both Chrome and Safari. (iMac4,1; Intel Core Duo; 1.83 GHz; with 2 GB RAM, running OS X 10.6.Cool


Sounds like you might have some firewall software running between your browser and our servers. That seems odd that you were able to download NeoOffice 3.2 as the same code is used on our servers to detect non-Mac search bots from flooding our server.

Are you running your Mac in an office or business? If so, does downloading it from another place like your home work OK? If yes, then that office or business is very likely filtering your web browsing.

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Mon Apr 25, 2011 10:42 pm    Post subject:

GridLox,

I looked at our web logs and search for the IP address of your last post. There is definitely something messing with your browsers connection to our servers.

Most browsers send a descriptive field to each web server that it visits that says the browser vendor, version, and type of machine that it is running on. For example, Safari on Mac OS X 10.7 Lion sends the following:

Code:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_7; en-us) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1


Your browser, on the other hand, sent the following:

Code:
Mozilla/5.0 (000000000; 0; 00000 000 00 0 000000; 00000) DDDDDDDDDDDDDDDDDDDD DDDDDDD DDDD DDDDDD DDDDDDDDDDDDD DDDDDDDDDDDDDDD


Either you are running some haxie that messes with your browsers or there is a server in between your machine and our server that is modifying what your browsers send to web servers.

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Tue Apr 26, 2011 12:02 am    Post subject:

Since we cannot trust getting reasonable data from your browsers, you can try using the cURL Terminal command to download the test patch. To do that, launch the /Applications/Utilities/Terminal application, copy the following commands into the Terminal window, and press the Return key. This will download the test patch to your Desktop:

Code:
cd ~/Desktop
curl -O http://joe.neooffice.org/test/NeoOffice-3.2-Patch-0-Test-1-Intel.dmg


Hope that helps.

Patrick
Back to top
sardisson
Town Crier
Town Crier


Joined: Feb 01, 2004
Posts: 4588

PostPosted: Tue Apr 26, 2011 12:43 pm    Post subject:

FYI, I posted an item about this "software corrupting the browser UA string and preventing downloads" problem in the NeoOffice Installation Issues FAQ.

Smokey

_________________
"[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Tue Apr 26, 2011 1:30 pm    Post subject:

FYI. I got a private message from another donor today that the test patch solves the same crashing bug for them so I have staged NeoOffice 3.2 Patch 1 with the fix.

Once GridLox has confirms that the test patch fixes the bug, I will release the official Patch 1 on our website.

Patrick
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Releases All times are GMT - 7 Hours
Goto page 1, 2  Next
Page 1 of 2

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.