Apache OpenOffice (AOO) Bugzilla – Issue 51683
Base Crashes, rest of OO.o crashes and weird errors appear
Last modified: 2008-05-18 00:09:39 UTC
I have an error report that wouldnt send, for the error reporting function also crashed. PROBLEM: I was using Base to create a report. I didnt have rights to change the database, but, only wanting to create a report, I thought it would allow it. I figured writing a report was only reading. However, I realize now I had the "open database for editing" box checked. When I selected two fields on the "form" wizard and clicked next, OO.o locked up. I forced closure. That's error #1. Then, when I recovered all my documents, I attempted to save them. I got a General Error: General input/output error, looking like this: "Error saving the document DataVision+SQL Service Reporting: General Error. General input/output error." Error #2. This occured, I guessed, because OO.o still read the documents as "open," and you can't open two of the same document and save it. So, I closed them all down. But when I tried to close Calc, I got a strange mirriade of errors, of which i remember none. However, it locked up as well, reading the file as closed and the program as open, reading the closed file. Or so I think. I am an amature programmer, and it could have been anything, including my OS (Microsoft is known for random little problems like this. I'm using Windows 2000). Anyway, I told it I wanted to debug, but since I can't understand assembly language, I copied this instead. This came when I recovered my files and then tried to send it. I crashed OO.o and recieved this error: "Unhandled exception in crashrep.exe (NTDLL.DLL): 0xC0000005: Access Violation." I hope this can help you guys! I love OO.o! Good luck!
*** Issue 51684 has been marked as a duplicate of this issue. ***
set oooqa keyword
sorry, my browser moved me to an issue in the list, I've unset the oooqa keyword, that I set by mistake
changed owner
Hi jordana309, Crashrep.exe crashing is known and fixed now, I believe. There were a lot of Base issues fixed in 2.0.1, could you try reproducing this with 2.0.1 and see if you can still get a crash?
No followup, wait two weeks -> WFM. Resolving.
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew