Created attachment 136108 [details]
macOS crash diagnostic report

No crash for me with LO5361, but perhaps I am misunderstanding how to reproduce the behaviour.

In step 3, when you write "Drag menu bar to external display", what exactly do you mean ?


My setup is Thunderbolt connection from MBpro 2015 to Apple Thunderbol 27" display 


I unset mirroring, then started LibreOffice from my MBPro, and dragged the StartCenter to the TB display monitor --- no crash.

Thanks for the quick response.

In Displays Prefs (in Arrangement tab), when Mirror is unchecked, the menu bar can be dragged from one display rectangle to another.

I did some more testing. Sorry, the arrangement and Mirror settings don't make a difference. When the external display is connected, LibreOffice crashes on startup. When I disconnect the external display, it runs.

The external display is connected to the HDMI port via an HDMI to DVI adapter. (The external monitor is an AOC e2450Swd, 24 inch, 1920 x 1080. I don't have a Thunderbolt display or any other way to connect this monitor.)

I have the Dock on the left. I tried moving it to the bottom, LO still crashes on startup with the external display connected.

I just installed LO 5.3.6.1, same behavior.

Created attachment 136125 [details]
macOS crash diagnostic report, LO 5.3.6.1

@DaviP :

- when you plug in the external display, what is the colour profile that is used by MacOS?

- do you have more than one graphics chip in your MBPro ? 

- if so, do you have any settings activated in System Preferences - Energy Savings relating to automatic switching of graphics chips ?

@DaviP : forgot to ask:

- do you have any Assistive Technology features activated (screen reader, VoiceOver, screen zoom, Dragon Dictate, etc) ?

The color profile for the external display is called 2450W. I've also tried several others, including "Generic RGB Profile", LO crashes with each.

The 2015 MacBook Pro has one Graphics chip. System info below.

I am not using Assistive Technology features.

Thanks.


Intel Iris Graphics 6100:

  Chipset Model:	Intel Iris Graphics 6100
  Type:	GPU
  Bus:	Built-In
  VRAM (Dynamic, Max):	1536 MB
  Vendor:	Intel (0x8086)
  Device ID:	0x162b
  Revision ID:	0x0009
  Metal:	Supported
  Displays:
    2450W:
      Resolution:	1920 x 1080 @ 60 Hz
      Pixel Depth:	32-Bit Color (ARGB8888)
      Display Serial Number:	DGNC6HA063261
      Main Display:	Yes
      Mirror:	Off
      Online:	Yes
      Rotation:	Supported
      Automatically Adjust Brightness:	No

@DaviP : can you change the resolution of the output on your external monitor ?

Does changing this (up/down) have any effect on whether you can start LO ?

I tried resolutions 1600 x 900 and 1280 x 720, LO still crashes on startup. (Default resolution is 1920 x 1080) Thanks, keep trying.  :-)

(In reply to Davi P from comment #9)
> I tried resolutions 1600 x 900 and 1280 x 720, LO still crashes on startup.
> (Default resolution is 1920 x 1080) Thanks, keep trying.  :-)

OK, so another suggestion I can make is for you to try and find a debug version of LO for OSX, download that and attempt to run LO from a lldb session and obtain a backtrace, as the problem seems specific to your particular setup (perhaps some hiDPI problem with the graphics chip in question?)

Unfortunately, there don't appear to be any LO5.4 debug-enabled developer versions currently for OSX.


Alternatively, by any chance, could you check your settings in Preferences > LibreOffice > View to see whether you've activated OpenGL ? By default, this is disabled (or should be disabled).

Created attachment 136345 [details]
LO View Options screenshot

OpenGL not activated. See attached View Options screenshot.

I don't know of anything unusual in my display setup.

I can start LO without an external display connected, and then connect the display and use LO normally. If I then quit LO and try to start it again, it crashes.

Doesn't the backtrace in the macOS crash report help to locate the problem?

Unfortunately, we need more information than the Apple traces provide. 


For some reason, at least as I understand it :


0   libvcllo.dylib                	0x000000010fbe152d Application::GetSolarMutex() + 13
1   libvcllo.dylib                	0x000000010f93a1ae SolarMutexGuard::SolarMutexGuard() + 14
2   libvcllo.dylib                	0x000000010fcbe634 -[VCL_NSApplication screenParametersChanged:] + 36
3   com.apple.CoreFoundation      	0x00007fff9e4ca45c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
4   com.apple.CoreFoundation      	0x00007fff9e4ca35b _CFXRegistrationPost + 427
5   com.apple.CoreFoundation      	0x00007fff9e4ca0c2 ___CFXNotificationPost_block_invoke + 50
6   com.apple.CoreFoundation      	0x00007fff9e487523 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1827
7   com.apple.CoreFoundation      	0x00007fff9e48655c _CFXNotificationPost + 604
8   com.apple.Foundation          	0x00007fff9feab677 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
9   com.apple.AppKit              	0x00007fff9c357ba2 -[NSApplication _reactToScreenInvalidationImmediately:] + 399
10  com.apple.AppKit              	0x00007fff9c3579df __44-[NSApplication _reactToScreenInvalidation:]_block_invoke + 59


The LibreOffice process doesn't like, or doesn't know how to react to a screen parameter setting that it receives from

NSApplication _reactToScreenInvalidationImmediately

but that might just be a red herring for some other problem.

That is why a full backtrace from a lldb session with a debug enabled build of LibreOffice would be useful here.

Alex, thanks for looking at the Apple crash report. I don't know how difficult it would be for me to install lldb and find a debug-enabled LO.

I just installed and tested LO 5.4.1, and it has the same problem.

I hope someone else will be able confirm this issue.

Looks like a variant of bug 103690. Should be fixed with LibO 6.0.2

*** This bug has been marked as a duplicate of bug 103690 ***