Bug 165505 - Options Dialog Unusable in 25.2 on macOS 15.3
Summary: Options Dialog Unusable in 25.2 on macOS 15.3
Status: RESOLVED DUPLICATE of bug 165277
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.0.3 release
Hardware: ARM macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-28 09:38 UTC by Iandol
Modified: 2025-02-28 17:17 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
spindump.txt from activity monitor (570.01 KB, application/zip)
2025-02-28 09:42 UTC, Iandol
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Iandol 2025-02-28 09:38:06 UTC
Description:
Since updating to 25.2 (I've tested both 25.2.0 and 25.2.1), the options dialogs are essentially unusable, suffering from extreme lag. This happens on open, where a blank window can stay on screen for minutes, but also when navigating or trying to change values in panels. LibreOffice shows ~100% CPU alongside WindowServer 100%, even with no widgets or buttons shown. Reverting to 24.8 and options works again. THere are no clear errors, and using Writer itself seems fine, just options causes the lag.

I deleted all my user settings and fully uninstalled LO and reinstalled, I still see this problem. I attach a spindump from Apple activity monitor when options dialog is frozen. 25.2 is wholly unusable on my system, luckily 24.8 works fine!

Steps to Reproduce:
1. Open options dialog.
2.
3.

Actual Results:
Severe hang

Expected Results:
Functional options dialog


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 25.2.1.2 (AARCH64) / LibreOffice Community
Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49
CPU threads: 8; OS: macOS 15.4; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Iandol 2025-02-28 09:42:27 UTC
Created attachment 199526 [details]
spindump.txt from activity monitor
Comment 2 Patrick (volunteer) 2025-02-28 14:44:50 UTC
I cannot reproduce this bug so I looked at your spin dump and noticed the following:

1. You are running macOS 15.4 which is a beta version
2. LibreOffice is waiting for some macOS system timer to finish
3. The macOS system timer appears to be trying to connect to the window server and keeps executing some system function called "kernel.release.t8112"

Maybe you have found a macOS bug?

Here's what I am running for comparison:

Version: 25.2.1.2 (AARCH64) / LibreOffice Community
Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49
CPU threads: 8; OS: macOS 15.3.1; UI render: Skia/Metal; VCL: osx
Locale: en-CA (en_CA.UTF-8); UI: en-US
Calc: threaded
Comment 3 Patrick (volunteer) 2025-02-28 16:37:09 UTC
(In reply to Patrick (volunteer) from comment #2)
> I cannot reproduce this bug so I looked at your spin dump and noticed the
> following:
> 
> 1. You are running macOS 15.4 which is a beta version
> 2. LibreOffice is waiting for some macOS system timer to finish
> 3. The macOS system timer appears to be trying to connect to the window
> server and keeps executing some system function called "kernel.release.t8112"
> 
> Maybe you have found a macOS bug?

I just saw a similar spin dump in tdf#165277 and that was captured on macOS 15.3.1 so this isn't limited to macOS 15.4.

Unfortunately, I cannot reproduce this on my machine but I'll take at look at the spin dump in tdf#165277 and see if I can find some potential pattern of what's going on.
Comment 4 steve 2025-02-28 17:02:56 UTC
When you say "options dialog" do you mean LibreOffice Settings (aka Preferences)?
Comment 5 Patrick (volunteer) 2025-02-28 17:13:23 UTC
(In reply to steve from comment #4)
> When you say "options dialog" do you mean LibreOffice Settings (aka
> Preferences)?

Yes. I see -[MainMenuSelector showPreferences:] in the spin dump so in this bug, LibreOffice has created the dialog and is waiting for the next macOS event.
Comment 6 steve 2025-02-28 17:17:14 UTC

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