Description: When I open old Writer documents with LibreOffice, the application freezes. It uses 70% CPU. It does not happen with newly created documents. Steps to Reproduce: 1. Double-Click on document in Finder. Alternative: Open LibreOffice, then open document 2. LibreOffice freezes. 3. Actual Results: LibreOffice freezes in different stages of displaying the document. Sometimes just a blank window opens, sometimes it displays part of the document, sometimes it displays all of the document and then freezes. Expected Results: LibreOffice should open document Reproducible: Always User Profile Reset: No Additional Info: Older versions also affected - 5.0.something (can't figure out due to upgrade) User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12) AppleWebKit/602.1.50 (KHTML, like Gecko) Version/10.0 Safari/602.1.50
Created attachment 128153 [details] Simple document that makes LO Writer crash
Created attachment 128154 [details] Crash report that goes to Apple after killing LO
Hi Marco, I am unable to reproduce a crash opening your test file w LO 5.2.2.2 on macOS 10.12. Which mac are you using? Exact Model and production year could be helpful. Could you please try resetting your user profile to make sure the issue is not related to that: https://wiki.documentfoundation.org/UserProfile#Resetting_the_user_profile
Hi Steve, thanks for taking the time to look into the issue. My computer is a MacBook Pro, 13 inch, end of 2011 Processor: 2.4 GHz Intel Core i5 Memory 8 GB 1333 MHz DDR3 Graphics Card Intel HD Graphics 3000 512 MB I replaced the harddrive with a Samsung SSD (already one or two years ago, not recently, never experienced any problems). I had tried to delete the user profile before filing the bug report, and just tried again - it does not help :-( LO crashes in versions 5.2.2002, 5.1.5002, 4.4.7002 on this file and my computer.
No repro using provided test document with Version: 5.3.0.0.alpha0+ Build ID: 18818e96a2f47cc8d5a0192655b2d401f2c1b676 CPU Threads: 2; OS Version: Mac OS X 10.12; UI Render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group No repro either with Version: 5.2.1.2 Build ID: 31dd62db80d4e60af04904455ec9c9219178d620 Threads CPU : 2; Version de l'OS :Mac OS X 10.12; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group Considering that the OP has integrated Intel HD graphics chip, I am of a mind to mark this as a DUP of bug 100994
@Marco : 1) Do you connect your MBPro to an external monitor ? If so, what resolution is that monitor running at ? 2) Try any of the following : (a) Setting color profile to "Color LCD" (which is default for built-in display) or "Generic RGB" (b) check whether the option "Automatic graphics switching" is (de)activated under Energy Saver in the General System Preferences ? Please also report whether toggling this option solves the problem.
Alex, you nailed it! It is the color profile that causes the problem. > 1) Do you connect your MBPro to an external monitor ? If so, what resolution is that monitor running at ? Yes indeed it is connected to an external monitor. It is an LG L227W, connected via DVI-D Resolution: 1680x1050 > 2) Try any of the following : > > (a) Setting color profile to "Color LCD" (which is default for built-in display) or "Generic RGB" The color profile was set to L227W. When I set it to "Color LCD" oder "Generic RGB" (I first have to untick "show only matching profiles"), then I can open the document and work with it normally. Once I switch back to L227W, the issue is back. > (b) check whether the option "Automatic graphics switching" is (de)activated under Energy Saver in the General System Preferences ? Please also report whether toggling this option solves the problem. This option does not exist on my MacBook Pro. I gather from this article it is only available at some models. https://support.apple.com/en-us/HT202043
So clearly there is a workaround that is good enough for me. If I can help any further on this bug (seems it is indeed a duplicate), please let me know. Big thanks to everyone involved, this is not my first bug report but the first one solving my problem.
*** This bug has been marked as a duplicate of bug 100994 ***