Bug 139653 - Time out when opening file browser dialog (open, save as, insert image) + host of other issues
Summary: Time out when opening file browser dialog (open, save as, insert image) + hos...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.4.1 rc
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-15 17:40 UTC by lotard
Modified: 2022-02-05 13:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of options (29.97 KB, image/png)
2021-03-06 06:43 UTC, lotard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lotard 2021-01-15 17:40:53 UTC
Description:
Sometimes (I can't reproduce it on call), when trying to open the file browser dialog (when opening a new document, 'saving as', saving a new document etc) LO will hang (rolling beach ball) for several seconds and then just pretend nothing happened. No window appears. Trying again results in the same thing. Only program restart helps.

This has been happening fairly often (once a day?) for several months now, not sure which version it started with anymore, no updates helped. Reseting user profile did not help.

Associated, but possibly unrelated issues:
- LO sometimes crashes when last active window is closed (ie a crash/recovery window appears without any documents in it)
- LO occasionally crashes otherwise
- LO sometimes crashes when opening a new document
- LO Calc sometimes grinds to a halt when entering new data - ie when I press enter it will hang for about 2-3 seconds before moving on. Program restart helps.

I have a feeling it may be related to memory exhaustion implying bad garbage collection. Or something like that.

I have no idea where to get any logs I could share to help diagnosd this problem. The guidelines I found on this were opaque and Linux-specific.


Steps to Reproduce:
'save as', 'open' etc

Actual Results:
beach ball, then nothing

Expected Results:
'file browser' opens


Reproducible: Sometimes


User Profile Reset: Yes



Additional Info:
"Use OpenGL for all rendering" is not even an option in my preferences.
Comment 1 lotard 2021-01-19 19:49:56 UTC
Any suggestions on how to diagnose/fix this problem? It's really quite annoying.
Comment 2 Dieter 2021-02-07 11:59:48 UTC
Lotard, thank you for reporting the bug. It seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ or with a master build from http://dev-builds.libreoffice.org/daily/master/current.html? You can install master alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 3 lotard 2021-02-14 19:12:12 UTC
I can confirm it persists in every version I have had for the past 6 months, incl. the latest one.

Also, 'safety mode' does not change anything.
Comment 4 Dieter 2021-02-14 19:29:17 UTC
(In reply to lotard from comment #3)
> I can confirm it persists in every version I have had for the past 6 months,
> incl. the latest one.

Please paste informations from Help => About LibreOffice
Comment 5 lotard 2021-02-16 05:56:08 UTC
(In reply to Dieter from comment #4)
> (In reply to lotard from comment #3)
> > I can confirm it persists in every version I have had for the past 6 months,
> > incl. the latest one.
> 
> Please paste informations from Help => About LibreOffice

Version: 7.1.0.3 / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 4; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-GB (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 6 lotard 2021-03-06 03:35:21 UTC
Any suggestions? How do I pull up crash report for example?
Comment 7 Dieter 2021-03-06 05:41:07 UTC
(In reply to lotard from comment #6)
> How do I pull up crash report for example?

If the option "Send crash reports" is selected in Tools => Options => LibreOffice => General the crash window should display link to crash report
Comment 8 lotard 2021-03-06 06:43:11 UTC
Created attachment 170262 [details]
screenshot of options
Comment 9 lotard 2021-03-06 06:47:14 UTC
Thank you, you are quite helpful.

The menus are different (LibreOffice->Preferences) and the options are as well (see screenshot), but I guess "Collect usage data" is the one?

I've also noticed "Use LibreOffice dialogs" in the same tab, which seems like an obvious thing to try - not that it was obvious such an option should even exist in the first place.
Comment 10 Dieter 2021-03-06 07:15:43 UTC
(In reply to lotard from comment #9)
> The menus are different (LibreOffice->Preferences) and the options are as
> well (see screenshot), but I guess "Collect usage data" is the one?

No, there should be another option [1], but I don't know, why you can't see it.

[1] https://help.libreoffice.org/7.1/en-GB/text/shared/optionen/01010600.html?System=WIN&DbPAR=WRITER&HID=cui/ui/optgeneralpage/OptGeneralPage#bm_id3539840
Comment 11 lotard 2021-03-08 05:40:43 UTC
(In reply to Dieter from comment #10)
> (In reply to lotard from comment #9)
> > The menus are different (LibreOffice->Preferences) and the options are as
> > well (see screenshot), but I guess "Collect usage data" is the one?
> 
> No, there should be another option [1], but I don't know, why you can't see
> it.
> 
> [1]
> https://help.libreoffice.org/7.1/en-GB/text/shared/optionen/01010600.
> html?System=WIN&DbPAR=WRITER&HID=cui/ui/optgeneralpage/
> OptGeneralPage#bm_id3539840

That is rather curious. Here's my version info, if that helps:

Version: 7.1.0.3 / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 4; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-GB (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 12 eisa01 2022-02-05 13:33:00 UTC
I think the first issue may be related to bug 128233

I'm going to resolve this given the variety of issues discussed and this being a very old report