Apache OpenOffice (AOO) Bugzilla – Issue 61112
Openoffice crashes when a wizard runs
Last modified: 2006-05-31 14:29:06 UTC
Unfortunatelty this includes the crash reporter. I cannot run the Base application in any meaningful way. I can send the crash report files if somebody tells me where to send them to. I have tried four different JREs. I have tried reinstalling 2.0.1 twice. I have shut down every visible process bar explorer and systray before I started.
Created attachment 33526 [details] The crash report error file
Changed priority to p3 for OP.
Hi, Please provide some more information about the crash please read http://qa.openoffice.org/issue_handling/basic_rules.html#reproducibility I close this issue now as INVALID. Feel free to reopen the issue, if you can provide more information how to reproduce this issue. Bye Marc
I am getting the wizard to crash on FreeBSD 6.0 2.0m151 when I go to file->wizards in a new text document.
Thanks xxjack12xx - it might be to do with wizards opening text documents - I do not know of this explains why the crashrep crashes as I have never seen one. Ok, I will try and give a couple of step-by-step examples. Open Base Select 'Connect to an existing database' choose 'Microsoft Access' and 'Next>>' Browse to the database and 'Next>>' 'Finish' Select 'Use wizard to create form' A windows dialog now appears that is headed 'Crashrep' with the normal text - This program has performed an illegal operation etc. Followed by another for Soffice. In restarting 2.0.1, a dialog appears Openoffice Org Document Recovery This lists the database and a document 'Untitled1' (showing that it had initiated the form.) Select 'Start Recovery' and 'Next>' Welcome to Openoffice.org 2.0 Error Report - and 'Next>' Sending the Error Report [enter text] and 'Send' A windows dialog now appears that is headed 'Crashrep' with the normal text - This program has performed an illegal operation etc. But the database does open as after 'Finish' above Repeat ad infinitum ad nauseam.
If you get crash reports with a crash even in the crash reporter whenever you open a Java applet in Windows, you might have a look into this thread: http://forum.java.sun.com/thread.jspa?threadID=661574 On my XP home system, I had anti aliasing enabled in the Nvidia driver. This crashed Java RTE. Some workarounds are given in the above thread.
OK thanks for the hints. I have been working on this. Firstly I must apologise for changing more than one thing at once when trying to fix this. Very amatuerish, sorry. Following the hints, I searched for settings ang selected Netscape/Mozilla in one of the JRE control pages. (I Use Mozilla.) This got me further. The next two are the debugging mistake so the order is irrelevant: If I first selected and viewed a table, that stopped the form from crashing! If I did not select and view a table, the form always crashed. In opening the database (after the crash recovery), I was always selecting 'Open' and not 'Finish'. It prompted me for the name and then for permission to overwrite the odb file. Instead I selected 'Finish' and not 'Open'. Having done this, I was able to open and modify the form and, having done that, it was then possible to open the form without it crashing without first having opened the table. Work that lot out. I cannot.
Right I have now tried this out on a multi-table-linked Access database. No amount of fiddling will get it to work. Normally it just crashes during the Form Wizard (near the end - as it is trying to get the data>) If I fiddle extremely hard, I can get a form icon but selecting just causes "The document [xxxx] could not ne displayed to come up". Trying to use this database cause the other to ihibit the same syptoms until I fiidle it back again (as previous posting.) It seems to be act of having to access the data that is the problem here. However the continuing crashing of crashrep must be an issue as well. I tuned logging on for Jave and got: # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_FLT_INVALID_OPERATION (0xc0000090) at pc=0x1f531ad2, pid=-473323, tid=4294492565 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_03-b07 mixed mode) # Problematic frame: # C [MSADRH15.DLL+0x1ad2] # etc. To which the Java website says: There could be many reasons for the JVM crash. We are currently investigating the exact root cause of this problem. Here is a list of some possible causes. * The applet or application that you were running may contain programming errors or bugs that caused the JVM to crash. * You may be running an older version of the Java Runtime Environment (JRE) which contains bugs that can cause the JVM to crash. I have downloaded the latest version so the first of the two should apply here. The "Test Java virtual machine" worked perfectly on my computer. I cannot use Base without this being fixed. It is a stopper. Is it possible to have the priority of this increased. From correspondanse I am not the only person to come across this.
Right I have now tried this out on a multi-table-linked Access database. No amount of fiddling will get it to work. Normally it just crashes during the Form Wizard (near the end - as it is trying to get the data>) If I fiddle extremely hard, I can get a form icon but selecting just causes "The document [xxxx] could not ne displayed to come up". Trying to use this database cause the other to ihibit the same syptoms until I fiidle it back again (as previous posting.) It seems to be act of having to access the data that is the problem here. However the continuing crashing of crashrep must be an issue as well. I tuned logging on for Java and got: # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_FLT_INVALID_OPERATION (0xc0000090) at pc=0x1f531ad2, pid=-473323, tid=4294492565 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_03-b07 mixed mode) # Problematic frame: # C [MSADRH15.DLL+0x1ad2] # etc. To which the Java website says: There could be many reasons for the JVM crash. We are currently investigating the exact root cause of this problem. Here is a list of some possible causes. * The applet or application that you were running may contain programming errors or bugs that caused the JVM to crash. * You may be running an older version of the Java Runtime Environment (JRE) which contains bugs that can cause the JVM to crash. I have downloaded the latest version so the first of the two should apply here. The "Test Java virtual machine" worked perfectly on my computer. I cannot use Base without this being fixed. It is a stopper. Is it possible to have the priority of this increased. From correspondanse I am not the only person to come across this.
added keyword: needmoreinfo, because issue seems to be not reproducable in current state
clu->protocol: like 'advisor' has written in a private mail, he has problems with java in general (also in other application) - so it make no sense to fix it in oo, even if it would be generally reproducable
=> close