| Summary: | FILEOPEN: Writer hangs on opening DOCX with small complex table - layout loop | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Valek Filippov <frob> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | helenrussian, priyanka.gaikwad, timur, vmiklos |
| Priority: | high | Keywords: | filter:docx, haveBacktrace |
| Version: | Inherited From OOo | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=61484 https://bugs.documentfoundation.org/show_bug.cgi?id=55917 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 104444, 104450 | ||
| Attachments: |
file with a problem
Bug 51785 - WinDbg session with FAILED_SOURCE_CODE Bug 51785 - WinDbg session from LO 5.1 alpha Debug with Procdump+WinDBG in LO 5.2+ |
||
Lubos, does this look like something quick? Or is it more complicated? Reproducable under Mac OSX 10.7.4; LO 3.6.0 beta 3 Created attachment 64013 [details] Bug 51785 - WinDbg session with FAILED_SOURCE_CODE Confirmed with: LO 3.5.5.3 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit LibreOffice is stuck with this file - unresponsive, creates new threads once in a while. I did memory dump after 20 minutes and processed it in WinDbg. Attached full WinDbg session with memory dump file loaded. Looks like a layout loop, the doc version has the same problem as well. reproducible with LO 4.0.2.2 (Win7 Home, 64bit) MSO 2007 opens the file without problems within a few seconds while LO crahes -> increased the importance reproduced under Fedora 18 LO 4.0.2.2 Restricted my LibreOffice hacking area *** Bug 75978 has been marked as a duplicate of this bug. *** (In reply to Tushar Bende from comment #8) > *** Bug 75978 has been marked as a duplicate of this bug. *** How did you check that 75978 is a duplicate? Created attachment 116023 [details] Bug 51785 - WinDbg session from LO 5.1 alpha Another backtrace with procdump. MODULE_NAME: sal3 IMAGE_NAME: sal3.dll FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_sal3.dll!osl_loadModule Looks like inherited. Created attachment 124067 [details]
Debug with Procdump+WinDBG in LO 5.2+
Looks different. I guess this one should be correct. svllo.dll sfxitemset
Repro with 6.0+. *** This bug has been marked as a duplicate of bug 58944 *** |
Created attachment 63889 [details] file with a problem Attached file hangs LO writer on linux and windows (maybe it takes too long to open -- I gave-up after ~10 minutes).