Bug 104696 - LibO keeps searching for tool tips when hovering over toolbars, if a corresponding helppack is missing and disabling it isn't possible; see comment 5
Summary: LibO keeps searching for tool tips when hovering over toolbars, if a correspo...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All Windows (All)
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 108684 (view as bug list)
Depends on:
Blocks: Too-Much-File-Access Language-Help-Packs
  Show dependency treegraph
 
Reported: 2016-12-15 12:42 UTC by Telesto
Modified: 2022-10-10 03:31 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Process Monitor Output LO5400 when hovering over toolbar (73.96 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-12-15 12:45 UTC, Telesto
Details
Process Monitor Output LO4463 when hovering over toolbar (42.09 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-12-15 12:46 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2016-12-15 12:42:09 UTC
Description:
Despite the fact that the help files are not installed, LibO constantly tries to read the help files when moving the mouse over toolbars and menu's. 





When moving the mouse of the toolbar, LibO always t

Steps to Reproduce:
1.Install LibO without Help files
1.Download Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx)
2.Start Writer and minimize it
3.Start process monitor. Set filter to soffice.bin
4.Check capture is enabled in process monitor
5.Restore Writer window and mouse the mouse over the toolbars

Actual Results:  
Lots of failing Directory query's: C:\Program Files (x86)\LibreOffice 4\help\nl	NO SUCH FILE	Filter: nl


Expected Results:
Only check if help files are available once at launch and disable Directory query's afterwards when no help is available 


Reproducible: Always

User Profile Reset: No

Additional Info:
Found in:
Version: 5.4.0.0.alpha0+
Build ID: d538d3d84172a74dfe97d59a6d3daf9a45459cab
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-12-14_00:28:59
Locale: nl-NL (nl_NL); Calc: CL

and in
Versie: 4.4.6.3 
Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d
Locale: nl_NL

but not in (seems language packs are integrated differently or it's because i'm using a portable edition in this case)
Version: 4.4.0.3
Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7
Locale: nl_NL


User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Telesto 2016-12-15 12:45:30 UTC
Created attachment 129664 [details]
Process Monitor Output LO5400 when hovering over toolbar
Comment 2 Telesto 2016-12-15 12:46:27 UTC
Created attachment 129665 [details]
Process Monitor Output LO4463 when hovering over toolbar
Comment 3 Buovjaga 2016-12-19 16:06:21 UTC
Repro with Process Monitor

Version: 5.4.0.0.alpha0+
Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-12-18_07:01:05
Locale: fi-FI (fi_FI); Calc: group
Comment 4 Telesto 2016-12-19 19:05:30 UTC
(In reply to Buovjaga from comment #3)
> Repro with Process Monitor
> 
> Version: 5.4.0.0.alpha0+
> Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a
> CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
> TinderBox: Win-x86@39, Branch:master, Time: 2016-12-18_07:01:05
> Locale: fi-FI (fi_FI); Calc: group

I forgot to mention the CPU drain. Hovering a bit around over the toolbar consumes between 3-5% CPU power. Same can be set for hovering a bit around in the deck. Switching hovering between deck and toolbar generates a CPU usage around 5% for brief moment.
Comment 5 Telesto 2017-01-31 11:35:09 UTC
The problem seems to be more nuanced and longstanding. In the past there - till LibO5.0.6.3 - where two types of Help tool tips:
- Tips
- Extended tips.

For both the tool tips the optional HelpPack is needed. However, the option to show 'Tips' was be enabled even without HelpPack installed.
Resulting in lots of disk query's accompanied with a noticeable CPU load when hoovering over toolbars (in search for ToolTips)
  
In the past the issue could be fixed by disabling Tips in Options -> General -> Help -> Tips. However option 'Tips' has been removed since LibO5.1.0.3.

It seems to me the problem can be resolved in multiple way's:
- Detecting the availability of HelpPack
- Add Tips to the main package (so it's installed by default) 
- Stop trying to reach helppack files after multiple reading failures.
Comment 6 Caolán McNamara 2017-01-31 13:23:16 UTC Comment hidden (obsolete)
Comment 7 Caolán McNamara 2017-01-31 13:27:12 UTC
wrong issue obvious, ignore that. Though in this case I'd rather expect "not* to query the helpcontent for non-extended tips, I feel that's the case to first investigate as to why that seems to happen
Comment 8 Telesto 2017-01-31 15:23:27 UTC
The non-extended tips behavior seems to be inherited from LibreOffice 3.3.0.
Comment 9 Telesto 2017-02-01 16:02:16 UTC
For testing purposes use LibO 5.3.0.3 or a daily build containing a language extensions (LibO is cycling through every directory).

The same behavior can also be seen when with Help Files installed and "Extended tips enabled" when hoovering over the properties deck.
Comment 10 Aron Budea 2017-07-01 00:02:59 UTC
*** Bug 108684 has been marked as a duplicate of this bug. ***
Comment 11 Aron Budea 2017-07-11 23:58:58 UTC
For reference, this commit was the one that removed Tips option, apparently it's always supposed to be on:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=0b0fb87fbac36ef9fbf3dfeac0f1372617f4b3e4

Not sure about the relation between help packs and tips, and what they're actually useful for.
Comment 12 QA Administrators 2018-10-24 02:56:37 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2022-10-10 03:31:23 UTC
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug