Bug 146431 - Hang when closing of newly created embedded HSQLDB ODB file (macOS)
Summary: Hang when closing of newly created embedded HSQLDB ODB file (macOS)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-12-27 10:30 UTC by Alex Thurgood
Modified: 2022-12-22 09:43 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Apple Stack Trace when hung office process (2.45 MB, text/plain)
2021-12-27 10:31 UTC, Alex Thurgood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Thurgood 2021-12-27 10:30:15 UTC
Description:
LibreOffice Dev (x86_64) hangs systematically when attempting to shutdown the application from a newly created embedded HQSLDB database file (ODB).

Oracle JDK 17 installed and recognized by LibreOffice under the Advanced preferences pane.

Steps to Reproduce:
1. Create a new HSQLDB embedded ODB file. 
2. Enter some data into a table.
3. Attempt to close the file
4. Instant hang


Actual Results:
See description above

Expected Results:
Should not hang, the app should either close the ODB file and return to dock, or else shutdown the running office process when requested (e.g. close app window).


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Oracle JDK 17 installed and recognized.
Creating the ODB file works just fine.
Comment 1 Alex Thurgood 2021-12-27 10:31:31 UTC
Created attachment 177151 [details]
Apple Stack Trace when hung office process

Enclosed is an Apple stack trace of the office process when hung.
Comment 2 Alex Thurgood 2021-12-27 10:33:46 UTC
Subsequent opening, editing of data, and closing of the ODB file appears to work correctly.
Comment 3 Julien Nabet 2021-12-27 16:36:05 UTC
Alex: is it a behavior on recent LO versions only?
Indeed, it makes me think about bugtrackers like tdf#77141 or tdf#57979
Comment 4 Alex Thurgood 2021-12-29 11:44:23 UTC
(In reply to Julien Nabet from comment #3)
> Alex: is it a behavior on recent LO versions only?
> Indeed, it makes me think about bugtrackers like tdf#77141 or tdf#57979

Julien, I only noticed this in fairly recent 7.3dev and current 7.4 branches.
As I don't systematically test everything against dev/dailies anymore, I can't be more precise.

It doesn't occur in production releases. 

This might have something to do with OS permissions as the dev/dailies aren't signed, and although on first startup LOdev asks for authorisation of some folders, it might be that that it doesn't ask for the permissions of all of the folders it is supposed to have permission for.
Comment 5 Alex Thurgood 2022-01-05 14:47:56 UTC
(In reply to Julien Nabet from comment #3)
> Alex: is it a behavior on recent LO versions only?
> Indeed, it makes me think about bugtrackers like tdf#77141 or tdf#57979

Re-reading tdf#77141, I shall have a look and see if I can get anything from the lsof output when it happens, although in my case, I don't need to have a 2nd file open for the problem to occur.
Comment 6 Alex Thurgood 2022-01-05 15:08:07 UTC
(In reply to Alex Thurgood from comment #5)
 
> Re-reading tdf#77141, I shall have a look and see if I can get anything from
> the lsof output when it happens, although in my case, I don't need to have a
> 2nd file open for the problem to occur.

Nothing left after quitting LO when searching for any remaining file descriptors, so the behaviour I'm seeing doesn't appear to fit what is being reported in tdf#77141.
Comment 7 Julien Nabet 2022-01-05 18:26:01 UTC
Thank you for your feedback.

It's a pity MacOs part isn't taken more into account. It seems the more macOS evolves (eg: security policies and recently new ARM CPU M1), the more pbs appear on LO :-(
Comment 8 Alex Thurgood 2022-01-06 11:16:25 UTC
(In reply to Julien Nabet from comment #7)
> Thank you for your feedback.
> 
> It's a pity MacOs part isn't taken more into account. It seems the more
> macOS evolves (eg: security policies and recently new ARM CPU M1), the more
> pbs appear on LO :-(


/OT RANT ON
To add misery to the existing situation, the current commercial provider for macOS versions of LO is clearly not, if at all, interested in fixing Base-related bugs, so the much touted "Get business support" that we put as a banner at the top of our download page is highly misleading. As a small business that is prepared to pay for the versions of LO from the AppStore for our 4 or 5 macOS machines, that is somewhat concerning.

Unless things change, I fear the day is fast approaching when I will have to drop working with LO altogether, as it is becoming increasingly difficult to use it reliably with databases of any sort, and without having to resort to contortions to do so, on macOS.
/OT RANT OFF
Comment 9 Alex Thurgood 2022-12-22 09:43:00 UTC
No longer reproducible in 

Version: 7.6.0.0.alpha0+ (AARCH64) / LibreOffice Community
Build ID: ad387d5b984c6666906505d25685065f710ed55d
CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded