Bug 45944

Summary:	FILEOPEN LibreOffice crashes opening just previously saved document
Product:	LibreOffice	Reporter:	Matthias Basler <libreoffice>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	critical	CC:	bugs, LibreOffice
Priority:	medium
Version:	3.4.4 release
Hardware:	x86 (IA32)
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	File reproducably crashes my LibO3.4.4 when trying to open it.

Description Matthias Basler 2012-02-11 15:24:00 UTC

Today I wanted to create a book, starting from a 110 pages plain text document. Formatted text, headings, inserted TOC and the first two images (in a frame).
Then I saved the document (again) and wanted to test whether formatting would still be OK after re-opening (which is known to be unfortunately not always the case).

But alas, the document will not open at all, LibO creates a notice about document recovery, but as expected the document recovery fails as well.

Unfortunately, since I always used the same filename throughout the day, I don't have any working version any more now. :-(

I don't want to attach the file publicly, but if anyone from the LibO developers wants it for fixing the problem, just drop me a note to "libreoffice at earthflight.org". The odt file is 1.23 MB large.

Used LibO 3.4.4 German.

Comment 1 Matthias Basler 2012-02-12 00:15:45 UTC

Additional notes/questions:
- This is on WinXP SP3
- Is there a way to write a trace file on Windows?
  (Only found comments for log files on linux...)

Comment 2 Rainer Bielefeld Retired 2012-02-12 00:55:59 UTC

@Matthias Basler:
What do you expect? Is that bug reproducible for you? I doubt that the damaged document will be useful, we need a source document to reproduce the problem.
For assistance concerning document recovery pease ask on a user mailing list.

Comment 3 Matthias Basler 2012-02-12 01:08:03 UTC

- With this document the crash is 100% reproducable.
- I do not consider the odt file itself damaged, since it loads fine in OOo3.3. Rather I believe that LibO3.4 runs into a bug when loading it, so providing the problematic file seems reasonable to get the bug reproduced by developers.

Comment 4 Matthias Basler 2012-02-12 01:11:27 UTC

Overwrote your edits. Sorry.

Comment 5 Matthias Basler 2012-02-12 12:53:54 UTC

Created attachment 56926 [details]
File reproducably crashes my LibO3.4.4 when trying to open it.

In case it is relevant: The above test file has following history:
1. Copied 110 pages plain text into new LibO document
2. Created styles and page styles needed for a book layout
3. Inserted footers with page numbers
4. Did hundreds of replacements and formatting corrections in text
5. Inserted images, removed them because it was impossible to achieve the wanted layout, then inserted full-page frame on page 5 and inserted image into that.
6. Saved file with LibO3.4
  -> This file could not be loaded with LibO3.4.4

7. Opened file in OOo3.3, removed almost all text, removed almost all headings and inserted Lorem Ipsum instead of normal text.
8. Saved test file with OOo3.3
  -> This file can still not be loaded with LibO3.4.4

Note: I have not yet tested the LibO3.5 branch on this file.

Now, this test case should get you going. If there are still questions, let me know.

Comment 6 Pedro 2012-02-14 11:53:09 UTC

> Note: I have not yet tested the LibO3.5 branch on this file.

File opens correctly in LO 3.5.0rc3 under Win XP Pro x86 SP3

Comment 7 Matthias Basler 2012-02-14 12:19:38 UTC

I updated to LO 3.5.0 final today and I can confirm it opens both the original problematic file and the test case without problems.

So, should I close this issue now or is it still relevant for the 3.4.x branch?

Comment 8 Roman Eisele 2012-04-30 09:27:12 UTC

(In reply to comment #7)
> I updated to LO 3.5.0 final today and I can confirm it opens both the original
> problematic file and the test case without problems.
> 
> So, should I close this issue now or is it still relevant for the 3.4.x branch?

I think we should close this bug report now because the bug is fixed on the 3.5.x branch (and 3.6.x, anyway), we encourage all users to switch to 3.5.x, and there will be no more updates to LibreOffice 3.4.x.

Therefore, closing the bug report as RESOLVED/WORKSFORME.

@our QA experts:
If it was wrong to close this bug report, plase forgive me ;-). Matthias Basler got no answer to his (good) question in comment #7 for 2 months now, and so I just thought I could help ... IMHO, closing old and invalid bug reports helps to find the bugs which are still present and important.