Created attachment 149429 [details]
Example file

Thank you for reporting the bug. But, I cannot reproduce this in

Version: 6.3.0.0.alpha0+
Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded

Still repro 
Version: 6.3.0.0.alpha0+
Build ID: ce01727e4d6779ea128aa1be09f4af8cad4e1854
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: threaded

STR
1. Open the attached file (with spellchecker enabled)
2. CTRL+A & CTRL+C
3. Press CTRL+N & CTRL+V
4. Keep repeating step 3 for 6-7 times

I repeated step 3 ten times but couldn't reproduce the bug

Version: 6.3.0.0.alpha0+ (x64)
Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-08_00:38:10
Locale: en-US (de_DE); UI-Language: en-US
Calc: threaded

(In reply to Dieter Praas from comment #4)
> I repeated step 3 ten times but couldn't reproduce the bug
> 
> Version: 6.3.0.0.alpha0+ (x64)
> Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c
> CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
> TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-08_00:38:10
> Locale: en-US (de_DE); UI-Language: en-US
> Calc: threaded

Argh, should have been more precise.. LibO is behaving normally, only noticing a heavy - never ending - load in the background (task manager).

Hello Telesto

Thank you for reporting the bug.
I have repeated step 3 for 7 times and pasted contents in all documents
I can not reproduce the bug in

Version: 6.2.1.2 (x64)
Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: CL


Version: 6.3.0.0.alpha0+ (x64)
Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-08_00:38:10
Locale: en-US (en_US); UI-Language: en-US
Calc: CL

Repro the neverending CPU load on Windows

Had to bibisect this twice as I first got a bad result (checked by git checkout the blamed one and then the previous one). With win32-6.0: https://gerrit.libreoffice.org/plugins/gitiles/core/+/3bf6c97029d26ddf20007c47ca6b68e5cc52d846%5E!/

tdf#112975 WIN correctly handle VclInputFlags::OTHER

Adding Cc: to Jan-Marek Glogowski

Another issue was previously blamed for this: bug 116370

Any chance for a small priority bump.. High Major, instead of Medium Major. The STR is quite artificial.. but it's hard estimate extend/scale of this bug. IMHO. 

Putting bug 124660 into see also; rather speculative..

(In reply to Telesto from comment #8)
> Any chance for a small priority bump.. High Major, instead of Medium Major.
> The STR is quite artificial.. but it's hard estimate extend/scale of this
> bug. IMHO. 
> 
> Putting bug 124660 into see also; rather speculative..

No need to ask, you have the power. Just use it within these guidelines: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg

(In reply to Buovjaga from comment #9)
> (In reply to Telesto from comment #8)
> > Any chance for a small priority bump.. High Major, instead of Medium Major.
> > The STR is quite artificial.. but it's hard estimate extend/scale of this
> > bug. IMHO. 
> > 
> > Putting bug 124660 into see also; rather speculative..
> 
> No need to ask, you have the power. Just use it within these guidelines:
> https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.
> jpg

Yes, I know I can change it. But the chart doesn't really fit.. There is no category.. for doing 'weird' stuff in the background which isn't affecting the functioning or performance.. Following the Priority Chart I end up at Low Trivial ;-)

I would even consider to High Critical.. but that's more guessing about the commonness..

Promoting this to highest (hope nobody objects). It's a horrible battery drain issue at minimum..

Tentative patch: https://gerrit.libreoffice.org/77040

This prevents Idles starving each other. WfM but will definitely needs some review. Would be nice to get some testing, before this is merged.

Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/383032c50a3e3354f04200ce984a47ab9d2c5c67%5E%21

tdf#123583 use TaskStopwatch for Writer Idle loop

It will be available in 6.4.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

@Telesto, could you please verify this issue on master? I can't reproduce it with an older version of LibreOffice for comparison

No repro with
Version: 6.4.0.0.alpha0+ (x64)
Build ID: d3d13140f0036c53aa74820b41acfeffa3572168
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-08-14_12:05:15
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL

As reference: repro with
Version: 6.4.0.0.alpha0+ (x86)
Build ID: a675fe37abc134cc5cbf54385ca99c8d1417ce2b
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-07-26_09:09:34
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL