Description: Exceptional high CPU usage when typing between to images Steps to Reproduce: 1. Open the attached file 2. Start typing (or holding a key) while monitoring CPU usage Actual Results: Pretty high CPU spike. Worst case 60%. Normal 30% Expected Results: Something like 4.1. So about 5% CPU usage Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 6.0.0.0.alpha1+ Build ID: b3f1d199a72ce87cb65ddaeac922564f57da6a4d CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-11-06_00:10:53 Locale: nl-NL (nl_NL); Calc: CL and in Versie: 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 but not in Versie: 4.1.0.4 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Created attachment 137892 [details] Example file
Created attachment 137894 [details] Callgrind output from master Repro. Was not related to auto spell checking. Possibly same as bug 112568? Arch Linux 64-bit Version: 6.0.0.0.alpha1+ Build ID: 121303615054568c204def97872343d2014af4a0 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on November 17th 2017
(In reply to Buovjaga from comment #2) > Created attachment 137894 [details] > Callgrind output from master > > Repro. Was not related to auto spell checking. > > Possibly same as bug 112568? > > Arch Linux 64-bit > Version: 6.0.0.0.alpha1+ > Build ID: 121303615054568c204def97872343d2014af4a0 > CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; > Locale: fi-FI (fi_FI.UTF-8); Calc: group > Built on November 17th 2017 It was indeed looking into bug 112568 when I found this, and it could be the same issue (it would surprise me). However not 100% sure. The letters appear nearly instantaneous; some lag, but not that obvious. And both reports are related to LibO5.4
The Callgrind trace seems to point to bug 86675 (BitmapScaleSuper) I attempted a bibisect with 4.1max, but nearly every version I did try kept crashing..
@Buovjaga This is dupe of bug 112568 (or the other way around)
Let's dupe to the older and I will ref my trace there. *** This bug has been marked as a duplicate of bug 112568 ***