Issue 107967 - Crashes, mostly when open / close document
Summary: Crashes, mostly when open / close document
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.2 RC1
Hardware: All Windows XP
: P2 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: crash
Depends on:
Reported: 2009-12-28 14:05 UTC by Rainer Bielefeld
Modified: 2017-05-20 10:01 UTC (History)
10 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

WinXP crash report (417.34 KB, text/xml)
2009-12-30 14:59 UTC, Rainer Bielefeld
no flags Details
Font Information (19.83 KB, application/pdf)
2010-01-21 07:40 UTC, Rainer Bielefeld
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Rainer Bielefeld 2009-12-28 14:05:35 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 ;-)
Comment 1 Rainer Bielefeld 2009-12-28 14:10:31 UTC
Crashed again, this time during mouse scroll. And again only announcement for a
crash report.
Comment 2 Rainer Bielefeld 2009-12-30 14:59:57 UTC
Created attachment 66913 [details]
WinXP crash report
Comment 3 Rainer Bielefeld 2009-12-31 07:39:17 UTC
For the latest crash I also was able to create an OOo crash report, ID is rgtqd2c
Comment 4 Rainer Bielefeld 2010-01-04 16:20:11 UTC
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
Comment 5 cno 2010-01-04 22:41:57 UTC
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..
Comment 6 Rainer Bielefeld 2010-01-08 18:37:25 UTC
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
Comment 7 Rainer Bielefeld 2010-01-13 13:08:42 UTC
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. 
Comment 8 Rainer Bielefeld 2010-01-14 11:35:05 UTC
An error report: ID rsf68wc 
Comment 9 Rainer Bielefeld 2010-01-14 17:38:02 UTC
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.
Comment 10 Rainer Bielefeld 2010-01-15 12:09:34 UTC
Some more crash report IDs: r5nn8wc, r2fh8wc
Comment 11 stefan.baltzer 2010-01-15 14:59:59 UTC
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?
Comment 12 cno 2010-01-16 22:20:16 UTC
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
Comment 13 Rainer Bielefeld 2010-01-19 19:01:49 UTC
Some more crash report IDs: rndd8wc, rxdd8wc, r82d8wc, rm2d8wc, r5wd8wc,
ruwd8wc, rd98fwc, rwugfwc
Comment 14 Rainer Bielefeld 2010-01-21 05:15:30 UTC
Due to crash risk
Comment 15 jbf.faure 2010-01-21 06:34:40 UTC
Add me to cc.
Comment 16 Olaf Felka 2010-01-21 07:29:05 UTC
@ rainerbielefeld: Can you answer to SBAs question?
Comment 17 2010-01-21 07:34:38 UTC
@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?
Comment 18 Rainer Bielefeld 2010-01-21 07:38:16 UTC
I sent a PDF with information concerning used fonts to SBA by PM.
Sorry, I will be away now for some hours.
Comment 19 Rainer Bielefeld 2010-01-21 07:40:38 UTC
Created attachment 67330 [details]
Font Information
Comment 20 merschmann 2010-01-21 07:59:17 UTC
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.
Comment 21 Rainer Bielefeld 2010-01-21 11:00:02 UTC
Another crash report ID: r2pm6wc

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

> is ... not yet confirmed ...

Let's wait for the official release :-/

What questions do you see without answer?
Comment 22 merschmann 2010-01-22 08:10:03 UTC
volkerme -> rainerbielefeld:
The questions maybe answered now, I did not refresh my window before submitting
my comment and you posted in between.
Comment 23 Rainer Bielefeld 2010-01-23 16:46:53 UTC
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.
Comment 24 2010-01-25 12:40:10 UTC
@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?
Comment 25 Rainer Bielefeld 2014-01-05 11:35:05 UTC
Has never been confirmed, so I close this one.