Bug 43570

Summary: FILEOPEN CRASH WordPerfect document: out of memory
Product: LibreOffice Reporter: Joost <joost11>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: CLOSED WORKSFORME    
Severity: critical CC: joost11, serval2412
Priority: medium    
Version: 3.4.4 release   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: WordPerfect document that crashes LibO Writer

Description Joost 2011-12-07 02:28:23 UTC
Created attachment 54174 [details]
WordPerfect document that crashes LibO Writer

When opening attached document, the soffice.bin process eats all available memory and then terminates. This document was created in WP 11 and was edited with WP X4 to anonymize it. Same behaviour for all my documents that were based on the same template. Many other WP documents open fine.

Running on Windows 7 x64, i7 CPU, 4 GB RAM.
Comment 1 bfoman (inactive) 2012-06-05 01:02:07 UTC
Checked with:
LO 3.5.4.2 
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

Could not reproduce.
Comment 2 Julien Nabet 2012-09-22 09:03:36 UTC
On pc Debian x86-64 with 3.5 branch updated today, I don't reproduce the problem.

Joost: could you give a try to last 3.5.X or 3.6.X version and tell us if it's ok?
Comment 3 Julien Nabet 2012-09-26 20:04:03 UTC
I put this tracker to RESOLVED/WFM.

Joost: don't hesitate to reopen if you can still reproduce the problem.
Comment 4 Joost 2012-09-27 12:35:29 UTC
Julien, sorry about the delay, but I can confirm that the problem is solved. Tested it today on the same computer. It still crashes on 3.4.4 but after upgrading to 3.6.1 the document loads fine.

Thanks for your attention, and keep up all the good work! This is a great project!


(In reply to comment #2)
> On pc Debian x86-64 with 3.5 branch updated today, I don't reproduce the
> problem.
> 
> Joost: could you give a try to last 3.5.X or 3.6.X version and tell us if
> it's ok?
Comment 5 Julien Nabet 2012-09-27 14:50:18 UTC
Joost: thank you for your feedback, I close the tracker (as WFM since there's no specific identified fix for it)