Description: Crash immediately after blank document Buttons look weird with icons on buttons showing at double width (still normal height) while buttons still have normal size. LO Freezes and then has to be force quit. Date/Time: 2016-10-20 18:11:58 +0200 OS Version: Mac OS X 10.12 (Build 16A323) Architecture: x86_64h Report Version: 25 Data Source: Stackshots Command: soffice Path: /Applications/LibreOffice.app/Contents/MacOS/soffice Version: 5.1.5002 (5.1.5002) Parent: launchd [1] PID: 19320 Event: hang Duration: 4.78s (process was unresponsive for 15 seconds before sampling) Steps: 48 (100ms sampling interval) Hardware model: MacBookPro11,3 Active cpus: 8 Fan speed: 3869 rpm (-164) -------------------------------------------------- Timeline format: stacks are sorted chronologically Use -i and -heavy to re-report with count sorting -------------------------------------------------- Heaviest stack for the main thread of the target process: 48 start + 1 (libdyld.dylib + 21077) [0x7fffb5b2f255] 48 main + 16 (soffice + 3872) [0x100dd8f20] .... Rest in attachment... Steps to Reproduce: 1. Open LO Writer 2. Click on "New document" in welcome screen menu on left 3. Writer opens, then freezes. Actual Results: LO Writer Freezes showing some blank, white rectangle over most of the UI. I have to Force Quit it. Expected Results: LO Writer should have opened and allowed document editing immediately. Reproducible: Always User Profile Reset: Yes. But exact same thing happens. Additional Info: Tried 5.1.0 and 5.1.5 I'm on MacOS. LO Writer has worked well until now. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 OPR/40.0.2308.81
Created attachment 128100 [details] Crash stack trace
Sounds like: https://bugs.documentfoundation.org/show_bug.cgi?id=100994
@Jarl, the mentioned bug has a workaround for affected user in Comment 90. Here is a direct link to that comment: https://bugs.documentfoundation.org/show_bug.cgi?id=100994#c90 Could you please test if this workaround fixes the crashing for you?
*** This bug has been marked as a duplicate of bug 100994 ***
The weird icon look is bug 100995