Apache OpenOffice (AOO) Bugzilla – Issue 107967
Crashes, mostly when open / close document
Last modified: 2017-05-20 10:01:58 UTC
Since I have changed from 3.1.1 to "Ooo 3.2.0 RC1 WIN XP DE-multilingual version German UI activated [OOo320m8 (Build 9472)]" for my normal work, I suffer from lots of crahes, especially with operations "open document", "send document", "follow hyperlink". I don't count the crashes, but it are much more than 10 a day. Unfortunately my OOo crash report tool is rather lazy ;-)
Crashed again, this time during mouse scroll. And again only announcement for a crash report.
Created attachment 66913 [details] WinXP crash report
For the latest crash I also was able to create an OOo crash report, ID is rgtqd2c
I tried again 2 days with a completely fresh new installation and new profile without any extensions. It seemed to work, I had only crash those 2 days, but today I restarted my normal quick work (as far as that is possible without my installed working aids), and today I had 7 crashes until now. The reason seems to eb "quick work" with many switches between documents, open and close, many edits ... . I'm sick from using this RC and have downgraded to 3.1.1
did not have any problems like that on Ubuntu. Possibly since I'm not yet so fast on this system? See if I hear any signals from Dutch Windows testers..
or the sake of completeness: After I have downgraded to 3.1.1 (for what also a Registry clean up had been required) the crashes vanished
It seems there has been some progress between RC1 and RC2 (Issue 108004 no longer reproducible), but those terrible numbers of crashes when I work intensively with OOo immediately reappeared when I upgraded from 3.1.1 to 3.2.0RC1.
An error report: ID rsf68wc
It seems that especially WRITER documents with lots of linked contents (Drawings, pictures) cause crashes. Sometimes these documents are destroyed after a crash, 3.2 will not be able to open them again, but they can be opened with 2.4.1 without any problems. Today I was able to create various crash reports, I will contribute ID asap.
Some more crash report IDs: r5nn8wc, r2fh8wc
SBA -> Rainerbielefeld: I showed the stack to HDU. Tho circle this in, please tell: (1) Which graphite-enabled font(s) do you use? (i.e. Gentium, Doulos, Charis...) (2) What version(s) are they?
I add an error report ID from my OOo320rc2 on xp: r8fqfwc - Just closed the database wizard successfull - switched to OOo 3.1 for a document - when I returned ... > crash
Some more crash report IDs: rndd8wc, rxdd8wc, r82d8wc, rm2d8wc, r5wd8wc, ruwd8wc, rd98fwc, rwugfwc
Due to crash risk
Add me to cc.
@ rainerbielefeld: Can you answer to SBAs question?
@rainerbielefeld: if I recall sba correctly some of the crash reports are related to "mail merge". Could you identify which of the crashids you mentioned were from sessions where mail merge was done?
I sent a PDF with information concerning used fonts to SBA by PM. Sorry, I will be away now for some hours.
Created attachment 67330 [details] Font Information
volkerme -> rainerbielefeld : This issue may be very disturbing for you but it is not yet confirmed as there is no reproducable scenario known. Therefore I removed it from the release blocker list. Please answer the questions from sba about your fonts to make further investigations possible for the engineers.
Another crash report ID: r2pm6wc @hdu: My crash reports for this issue are marked with "This is a crash report for Issue 107967". Pls. excuse me if I mentioned an ID for an other Issue here @volkerme > is ... not yet confirmed ... Let's wait for the official release :-/ What questions do you see without answer?
volkerme -> rainerbielefeld: The questions maybe answered now, I did not refresh my window before submitting my comment and you posted in between.
Here you find 2 final crash report IDs: ryf5bwc, rrjxbwc I had to downgrade to 3.1.1 (what required a fresh new user profile, 3.1.1 did not run with my 3.2.0 profile), because the heavy damages 3.2 inflicted to my documents are no longer acceptable for me. So I have terminated my testing for 3.2.
@gh: AFAIK the crash report infrastructure has been killed by the cygwin changes on wntmsci12. Having the infrastructure working is very important for such issues as this. Is there another way to evaluate the crash reports than by using it? When will it work again?
Has never been confirmed, so I close this one.