Bug 93425 - Writer crashes when opening
Summary: Writer crashes when opening
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.5.0.0.alpha0+ Master
Hardware: All Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-14 12:21 UTC by Mike
Modified: 2017-02-28 08:35 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
2 versions of same file (3.73 MB, application/zip)
2015-08-14 15:28 UTC, Mike
Details
Backtrace of crash from 1.odt (11.82 KB, text/plain)
2015-09-14 16:08 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2015-08-14 12:21:00 UTC
Writer 5.0 crashes when attempting to work with my file (see attachment). The file gets opened, but about 30 seconds later, this is what I get:

---------------------------
LibreOffice 5.0 - Fatal Error
---------------------------
SEH Exception: ACCESS VIOLATION
---------------------------
ОК   
---------------------------

When reopening, it tries to restore the file, but crashes again (sometimes I get "SEH Exception: unknown").

Writer 4.5 seems to work with this file, but screws up most cross-references, so the text is completely broken.

More specifically:

I have a previous version of the file (1.odt), cross-references look OK.
In the latest version (2.odt) they are broken.
Pasting stuff from 2.odt to 1.odt breaks cross-references in 1.odt.


PLEASE HELP!
Comment 1 Julien Nabet 2015-08-14 15:04:40 UTC
Mike: there's no attachment here.
You can add one by using this link:
https://bugs.documentfoundation.org/attachment.cgi?bugid=93425&action=enter

(have in mind that any attachment is automatically made public so remove any private/confidential part)

Also, about the crash you can give a new try after having renamed your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows)
Comment 2 Mike 2015-08-14 15:28:23 UTC
Created attachment 117916 [details]
2 versions of same file

1.odt - cross-references look fine but many don't work (e.g. on p.26 where it says "В некоторых случаях после /x/ (см. 1.2.3)" - this is a ghost reference. Updating the contents at the end will ruin most cross-references (so they will look broken in addition to being broken).

2.odt - cross-references already look broken.

I don't think the file is corrupted, since the same happens with its really old versions which have always behaved perfectly.
Comment 3 Julien Nabet 2015-08-15 18:04:47 UTC
on pc Debian x86-64 with master sources updated yesterday, the file isn't loaded after more than 1 min (I gave up then)
I noticed a lot of these console logs:
warn:sw.core:1577:1:sw/source/core/doc/docbm.cxx:379: MarkManager::makeMark(..) - refusing to create duplicate CrossRefBookmark
warn:legacy.osl:1577:1:sw/source/core/unocore/unobkm.cxx:254: <SwXBookmark::attachToRange(..)> - could not create Mark.
warn:legacy.osl:1577:1:xmloff/source/text/XMLTextMarkImportContext.cxx:421: CreateAndInsertMark: cannot insert?

Idem with 2.odt (except there's no console log)
Comment 4 Mike 2015-08-15 20:37:40 UTC
Thanks! So what should I do?
What can be done with those bad references?
The thing is, there's no such problem with Writer 4.4.2.2. Does this mean I have to forever stick with that version?
Comment 5 Julien Nabet 2015-08-15 20:52:14 UTC
For the moment, yes, I should stick with previous version (just my opinion of course).
Certainly someone, QA or dev, will have some insight about this.
Comment 6 Mike 2015-08-15 21:50:21 UTC
Thank you!
Comment 7 Preben Hedegaard 2015-08-31 21:02:41 UTC
I found the same bug in Calc:

LibreOffice 5.0 - Fatal Error
---------------------------
SEH Exception: ACCESS VIOLATION

and after reopening Calc, the file restore enters an endless loop of restore operations, i got out of it by selecting "Ignore restore" and then i got the option to save the document in another location, with no data loss

In my case the bug was initiated by clicking "print preview"!

I can't reproduce the Bug
Comment 8 Buovjaga 2015-09-14 16:08:11 UTC
Created attachment 118710 [details]
Backtrace of crash from 1.odt

Win 7 Pro 64-bit, Version: 5.0.1.2 (32-bit)
Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261
Locale: fi-FI (fi_FI)
Comment 9 raal 2015-10-29 08:19:42 UTC
Crash file  1.odt in Version: 4.5.0.0.alpha0+
Build ID: 57d6b92b69a31260dea0d84fcd1fc5866ada7adb
Comment 10 QA Administrators 2016-11-08 11:57:24 UTC Comment hidden (obsolete)
Comment 11 Xisco Faulí 2017-02-28 01:46:01 UTC
I can no longer reproduce the crash in

Versión: 5.3.0.3
Id. de compilación: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
Subpr. de CPU: 1; Versión de SO: Windows 6.1; Repr. de IU: predet.; Motor de
trazado: HarfBuzz; 
Configuración regional: es-ES (es_ES); Calc: group

Closing as RESOLVED WORKSFORME

Feel free to move it back to NEW if you can still reproduce the issue on your
side.
Comment 12 Buovjaga 2017-02-28 08:35:51 UTC
Yep, both files now open on the same computer that I earlier reproduced the crash.

Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+
Build ID: eb7b03b052ffe8c2c577b2349987653db6c53f76
CPU threads: 4; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2017-02-26_22:34:18
Locale: fi-FI (fi_FI); Calc: CL