Bug 40887

Summary: Freeze when opening USPS Change of address document (FILEOPEN)
Product: LibreOffice Reporter: Laurence 'GreenReaper' Parry <greenreaper>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: ilmari.lauhakangas, sasha.libreoffice
Priority: medium    
Version: 3.3.4 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: USPS change of address form (broken)
USPS change of address form (working)
USPS change of address form (working)

Description Laurence 'GreenReaper' Parry 2011-09-14 12:43:35 UTC
Created attachment 51212 [details]
USPS change of address form (broken)

The attached document (PS Form 3575, which is fairly widely used, being the US Post Office change of address form) causes a freeze in LibreOffice Writer on several machines.

At the time of the freeze, the menu bar is not displayed, but the rest of the client area is (other than the document area, which is blank grey). The process appears to be stuck in a loop. Debugging suggests the issue may be somewhere in swmi.dll, drawinglayermi.dll or svxcoremi.dll, but it's possible that they're just being called repeatedly.

Notably, the second attached version of the same document does load.
Comment 1 Laurence 'GreenReaper' Parry 2011-09-14 12:43:57 UTC
Created attachment 51213 [details]
USPS change of address form (working)
Comment 2 Laurence 'GreenReaper' Parry 2011-09-14 12:44:38 UTC
Created attachment 51214 [details]
USPS change of address form (working)
Comment 3 Laurence 'GreenReaper' Parry 2011-09-14 12:49:45 UTC
Let me clarify that to "sometimes works and sometimes freezes like the rest". :-/

The document does have a number of small boxes for the address; maybe there is an issue with their layout?
Comment 4 Björn Michaelsen 2011-12-23 12:37:01 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 5 sasha.libreoffice 2012-02-02 08:23:00 UTC
reproduced in LibO 3.3.4 and 3.6.0 master on Fedora 64 bit
Comment 6 A (Andy) 2013-05-08 21:21:34 UTC
for me not reproducible with LO 4.0.2.2 (Win7 Home, 64bit), but it takes 3 to 5 seconds to open the file, MSO 2007 opens the file without any delay
Comment 7 Laurence 'GreenReaper' Parry 2013-05-08 22:13:30 UTC
On 4.0.2.2 (Win7 Home Premium, x64), on a CPU-limited but normally quite usable machine (X120e/E-350), the first form takes 55 seconds to load (using all of one core), while the second takes 9 seconds. Memory usage increases ~1MB/sec during load. Both documents are laggy when scrolling, selecting text, etc. Loading of other documents is blocked during the initial document load.
Comment 8 sasha.libreoffice 2013-05-11 06:29:19 UTC
in 4.0.2 on Fedora (RFR) 64 bit loading of first attachment takes 27 seconds
(CPU Pentium Core 2 Duo 1.8 GHz)

During loading LO is unresponsive. It is not an acceptable situation. At least should appear message "Loading ...". But it is not implemented. It would be better to appear message with working button "Cancel opening document".
May be it should be as separate bugreport.
Comment 9 A (Andy) 2013-05-11 09:07:57 UTC
Note to comment 6: I had tested it on an i5 with 2,4 GHz and 4GB RAM

And I tested it once more and for me it opens much faster than as for Laurence and Sasha.
Comment 10 Buovjaga 2014-10-21 11:48:45 UTC
The file labeled broken doesn't freeze, opens in like 10 secs. Version: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33
Comment 11 Laurence 'GreenReaper' Parry 2014-10-21 12:10:22 UTC
Well, it's a lot better than it was, though I would say that it now freezes for 10 seconds rather than not freeze at all.

The "working" version is even faster, so clearly there's something odd about the "broken" one. But perhaps this is sufficiently good?