Bug 150581 - LibreOffice locks up when switching from background to foreground on Mac
Summary: LibreOffice locks up when switching from background to foreground on Mac
Status: RESOLVED DUPLICATE of bug 148435
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.3 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 150844 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-08-24 09:57 UTC by Glob Design
Modified: 2022-12-13 09:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glob Design 2022-08-24 09:57:36 UTC
Description:
Open a text document that is fairly long and contains a lot of photos.

Make some changes, save the file but leave it open.

Switch to some other app like a browser and do something.

Command-tab back to LibreOffice and save again.

Now try to do some work or scroll.

LibreOffice locks up with spinning beachball and has to be force-quit.

100% reproducable on a Mac.

Steps to Reproduce:
1 Open a text document that is fairly long and contains a lot of photos.

2 Make some changes, save the file but leave it open.

3 Switch to some other app like a browser and do something.

4 Command-tab back to LibreOffice and save again.

5 Now try to do some work or scroll.

6 LibreOffice locks up with spinning beachball and has to be force-quit.

7 100% reproducable on a Mac.

Actual Results:
LibreOffice locks up with spinning beach ball and has to be force-quit, making the app unusable for any serious writing.

Expected Results:
It shouldn't lock up on switch to background and back. It should continue to work normally.




Reproducible: Always


User Profile Reset: Yes



Additional Info:
Please fix this. It makes the app unusable.
Comment 1 Michael Warner 2022-08-24 13:20:55 UTC
Please attach a sample document that demonstrates this behavior. Be sure to remove any confidential information.
Comment 2 Alex Thurgood 2022-08-24 15:24:31 UTC
@Glob Design: 

Context switching has been known to cause a hand/crash on macOS. This has been reported elsewhere, but can be difficult to reproduce, as it sometimes seems to be dependent on particular versions of either LO, or macOS.

In addition to the sample document requested by Michael, please provide the version of macOS that you are using, and whether or not you are using the Intel or Arm build version of LibreOffice.
Comment 3 Glob Design 2022-08-25 00:20:43 UTC
Hardware Overview:

  Model Name:	iMac
  Model Identifier:	iMac18,2
  Processor Name:	Quad-Core Intel Core i7
  Processor Speed:	3.6 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	8 MB
  Hyper-Threading Technology:	Enabled
  Memory:	32 GB
  System Firmware Version:	451.140.1.0.0
  OS Loader Version:	540.120.3~19
  SMC Version (system):	2.40f1
  Serial Number (system):	D25WV098J1G9
  Hardware UUID:	8BB2F171-3056-5B57-891A-6F21ABC1AA19
  Provisioning UDID:	8BB2F171-3056-5B57-891A-6F21ABC1AA19

I should also note I am using an ancient 30" Apple Cinema Display connected over MiniDisplay Port dual-link/Thunderbolt Adapter. The old display works fine in most cases.

I have also determined that the bug has something to do with using the Command key. Command-tab to switch back to LibreOffice will cause it but only if edits to the document have been made or a save has previously been done. It also happens if you obscure the document window with another app then swtich back.

Option-click on the desktop to hide LibreOffice, then switch back via Command-Tab also casues the crash.

I am using an Intel Mac - it's a 2017 iMac 21.5" model with 256GB internal SSD and several external drives, although LibreOffice app itself is running from the main Applications folder.

Also my document does have many photos in it, but I have seen the crash in many different documents.
Comment 4 Glob Design 2022-08-25 00:28:11 UTC
(In reply to Michael Warner from comment #1)
> Please attach a sample document that demonstrates this behavior. Be sure to
> remove any confidential information.

The documents in question are books I am writing so I don't want to attach them.

File size if 58.2MB for 1 chapter (1 chapter per file).

I should also note the files contain many photos which I dragged in from another drive. After relaunching LibreOffice after a crash it always throws an alert asking if I want to reconnect the external links, to which I always say yes.

It does it's little recovery thing each time, then the document opens where I left off:

"The document I-Left-8%20copy%204.odt contains one or more links to external data.

Would you like to change the document, and update all links
to get the most recent data?"

Another note is the documents live on a different drive from the inserted photos. Most of the photos have been edited down and are small - 300K - 3MB-ish and are mostly .png format. But there are dozens of them per file.
Comment 5 QA Administrators 2022-08-25 03:44:51 UTC Comment hidden (obsolete)
Comment 6 Alex Thurgood 2022-09-07 13:08:26 UTC
*** Bug 150844 has been marked as a duplicate of this bug. ***
Comment 7 Alex Thurgood 2022-09-07 13:17:57 UTC
I have had this happen to me, but can't reproduce it reliably and systematically on

Version: 7.4.0.3 / LibreOffice Community
Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a
CPU threads: 8; OS: Mac OS X 12.5.1; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR
Calc: threaded

However, given that a second user has reported the same issue, am confirming.
Comment 8 Alex Thurgood 2022-12-13 09:54:03 UTC
@Glob : please check with the latest 7.5 developer preview version available from the LibreOffice download site.

A fix has recently gone into 7.5 alpha that should resolve this issue.
Comment 9 Alex Thurgood 2022-12-13 09:59:12 UTC
Please retest with the developer preview version of 7.5 available from the LibreOffice download page.

A fix has recently been made available which appears to solve this issue.

Marking as a DUP of bug 148435

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