Created attachment 21470 [details]
Print screen of error

What version of Openoffice are you using? (1.9.xx)

Hello,

This is also a problem I am having (exactly the same to what you are)

I am running Open Office 1.9.77
I have Windows 98SE
I am running the latest version of Java

My Computer Specs:

PIII 450Mhz
Voodoo 2 Graphics Card
128mb SD Ram

My problem occured when I had a Calc document open. This contained 2 Data 
Sheets and 6 Pie Charts. The computer has been running very slow with this 
document.

I then went to open a Writer document as soon as this happened Open Office 
crashed and I was told I would have to recover my documents and they'd been 
saved.

I tried this numerous times but each time getting the same error when I was 
just about to submit the error report.

Note: There was hard drive activity and I am assuming whilst this was happening 
Open Office was loading in the background. I think this is what caused the 
error but I could be wrong.

The fact is I have been unable to send my error report and it's been very 
difficult to get Open Office up and running again. Repairing it did not work. I 
had to fully uninstall remove all folders and restart.

This then removes me having to recover the files but as it stands I cannot open 
the files that need to be recovered without continually going through the same 
loop. What can I do?

I am running Fix It Utilities version 5 with a virus scanner. I have noticed 
this does effect my system resources (and I have to disable it whilst going 
through the installation process)

Finally what might need to be brought to your attention is I have 
IntelliCluster (also bundled with the same software) this monitors program 
execution so that it can defragment my hard drive better. I also disable this 
when installing Open Office.

If you have anymore questions please feel free to ask and I will attach a 
screenshot of the error I get. 

Created attachment 22568 [details]
This is a screenshot of the error I am getting.

I've had the Crash Reporter utility crash on my PC several times also, although
it works most of the time. I have a Microsoft Windows application error report
file that was generated by XP, if that would be of any help. If you would like
to see it, please contact me and I will send it.

Windows XP Pro SP2
Hotfixes to 2/05
Java JRE 1.4.2_06
Build 680m77

Ed Z

Matius_4, can you attach the file that is causing this issue?

Created attachment 22934 [details]
This is the problematic file

Sorry for the delay - I wasn't notified of your reply :-)

You may not notice the problem with the file straight away open office crashes 
when I click on the arrow to see more of my sheets (there are 8 in total when I 
load it up I can only see one so I scroll to the right)

As soon as I click on that arrow - the program crashes and everything else I 
have said after...

Confirmed!

Using 1.9.79 on Win 2000 SP4, Calc promptly started acting very weird when I
opened this file. It opened okay, but when I switched from Calc to my browser
and back, the graph was gone, the text and icons of the buttons were gone, and
clicking in the cells caused little graphs to appear all over the Calc window. I
know I wouldn't believe it if it hadn't happened to me either.

Once I tried to close the app I was presented with a myriad of application
errors and GPFs.. 

Changed the component to Spreadsheet. Changing reported version to 680m77 since
that was the first reported in the comments. Subcomponent is UI now.

Hi,

the crashreporter isn't the spreadsheet, so I changed the component and
re-assign this Issue.

Frank

Hi thanks for the prompt confirmation of this bug!

Now the issue has changed to the crash reporter - will all issues regarding the 
spreadsheet I submitted be fixed also?

I'm sorry if this sounds a silly question I'm just a little tired and 
confused! :D

"Hi,

the crashreporter isn't the spreadsheet, so I changed the component and
re-assign this Issue.

Frank"

This is what threw me :D. I am having trouble with that spreadsheet and also 
when trying to recover the document the crash reporter - crashes

So I guess this is two bugs in one.

Best Wishes

Matthew

matius_4 -> I only recently started on OOo, so I'm not an expert on their
process. I can tell you in general, though, that bugs are assigned priorities on
how severe they are, and those priorities determine what gets fixed before a
release. When you look at the Priority link (above, 2nd column, 4th item down),
you can see what the priorities mean. Priorities do have meaning, but depending
on other factors those priorities can change, so fixes may not always happen in
the next version. We do aim for having relatively bug-free releases on the next
version, though.. :)

haxwell-> Thanks for the explination I have looked at the priority in the help 
and if I'm honest I think this issue should be put into the P2 category. As I 
have lost data with this error. I'm unable to use this file until this issue is 
fixed. This is just a request :D I don't mean to put my foot down. I am a 
student you see and these files rely on deadlines as I'm sure you'll understand.

I understand I took a risk using beta software but the sooner this is fixed the 
better.

Best Wishes

Matthew

I have beta 2 of OO (1.9.79) - running win xp SR 2 - and my crashrep.exe has 
crashed every time when OO base has successfully "reconstituted" a small .mdb 
file (contacts) I had tried to open with OO base and is trying to report the 
results.

Bob Riley in Albuquerque

With 1.9.87 no button appears to restore the document nor a Next button to send 
an error report. I had the cursor on the top of page 2 (empty page) and I tried 
to insert a file onto that page. I am using Windows ME.

Harold

I encountered this one also.  I was using Base and the Data Source Browser
previously.  No error noticed on exit at end of day.  Next morning, OOO reports
that the Base file (ODBC link) needed recovery.  Crashrep popped up to report
the nonerror.  OOO continued to load without problems but crashrep crashed when
report was sent.  Debug data will be submitted.

Created attachment 24250 [details]
crash report data

Crash report data submitted.  Includes Dr. Watson report, dump, and Dependency
Walker (http://www.dependencywalker.com) reports on crashrep.com and
crashrep.exe files.  System is WinXP Pro SP2, OOO 1.9.87 (previous beta
uninstalled first).

*** Issue 44281 has been marked as a duplicate of this issue. ***

This happened before. It seemed fixed for a while, but now it happened to me
with 1.9.88 on Win XP no sp2.

Is this the same as 38758?

reassigned to ja

mci -> ja:
please have a look , thanks...

JA->HRO: please have a look at this. Maybe it's a duplicate (Win98SE).
JA->Martius_4: please delete the file Recovery.xcu within your Windows user profile.

Hi Ja,

I don't actually have my Windows 98 SE machine anymore. I have upgraded to 
Windows XP SP2.

What will happen when I have deleted Recovery.xcu? Will this fix the problem?

I am a little confused about where this bug issue is going. Is this now a 
confirmed bug? I can see there are a few duplicates but what's the status of 
this one.

If I'm honest I can't really see what's been done to sort it out.

Thanks for your time

Matthew M 

I am still getting this issue on my new machine now. I have windows XP SP2.

I will attatch the file below which is an .xls file. This document will load 
in Microsoft Excel but when trying to open it in Open Office it brings the 
Crash Reporter up. It does not show up in the documents that it can recover 
either.

Thanks for looking at this.

Created attachment 25115 [details]
This is another file that will crash Open Office in .xls format

Matias,

I just tried your first spreadsheet (the .ods one), with 1.9.93, and it opened
and was navigable and editable with no hint of trouble.

However, the .xls sheet crashed the app right away, about halfway along the load
progress bargraph, which said "calculating"

Matt

*** Issue 44930 has been marked as a duplicate of this issue. ***

.

*** Issue 46088 has been marked as a duplicate of this issue. ***

Crashrep has just crashed on me, for the second time in 2 days.  The report was
"Crashrep has caused an error in kernel32.dll".  On both occasions the original
crash was while I was working on a table (not in the same document both times)
in Writer 1.9.100.  My operating system is Windows ME.

And again, this time the original crash was in a text document.  It seems that
crashrep crashes my computer every time it tries to send a report.
Are there any ideas about what is causing ths?

Thanks MJ for looking at this. I'm sorry I've been ages getting back to you on 
this.

Do I need to file the problem with the .xls file in a new bug report? Or will 
this bug be fixed within this issue?

I assume this is now properly confirmed. What exactly is going to be fixed? 
Will the recovery document process also be looked into?

I am also experiencing this crashrep.exe crashing problem on the latest build
(1.9.122).  I am attaching the drwatson log which was generated as a result of this crash -- hopefully it will be of some use.

Created attachment 28928 [details]
drwatson log of crashrep.exe crash.

hro@jhansonxi: The dmp file generated by dr. watson can be very helpfull to find 
the reason for the crash. Unfortunately the dmp you attached is from m87, where 
the debug informations needed to resolve the dump are no longer available. If you 
can reproduce the bug can you generate a dump based on a newer version (m106, 
m112, m115 or higher) ?
If you don't have a reproducable crash in OOo to bring the error report up you might 
simulate a crash on windows with a tool that is build in the sal module. It's a kill 
tool that acts like the unix kill command:

kill.exe -NULL soffice.bin

should let OOo crash.

The crashrep.exe might crash on sending the data if old incomplete crash data 
files are availiable.

Why is this issue marked Status: RESOLVED, resolution: FIXED.  There does not
seem to be anything here about it being fixed.

It crashed for me yesterday, using OOo_2.0.0rc1 on Windows ME.

Additional comments from materthron Thu Nov 3 06:01:48 -0800 2005 have been
added to issue 46088 (closed as duplicate of this) 

It seems OOo.2.beta still had the problem.

One way or another this still needs looking at, I'm afraid.

*** Issue 58255 has been marked as a duplicate of this issue. ***

*** Issue 58803 has been marked as a duplicate of this issue. ***

*** Issue 58670 has been marked as a duplicate of this issue. ***

.