Description: High CPU usage inserting a table in a large document Steps to Reproduce: 1. Open attachment 145054 [details] without spell checker enabled 2. Insert a table (say 2x2) after the first paragraph ("Wrist?") 3. Monitor CPU usage 4. Delete the table (monitor CPU usage again) Actual Results: 20 seconds 100% CPU usage (straight line) with 6.2 16 seconds 100% CPU usage (straight line) with 5.2 11 seconds fluctuating usage (+/- 90) with 5.1 Barely noticeable with 4.4.7.2 Expected Results: Something like LibO 4.4.7.2 Reproducible: Always User Profile Reset: No Additional Info: Found in: Version: 6.2.0.0.alpha0+ Build ID: 7d242f3bd7277236046f90d3f32b9792fd8ea97b CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-09-18_23:43:19 Locale: nl-NL (nl_NL); Calc: CL also noticeable in MacOS
The Word counter will restart when inserting the table Attempted a bibisect using LibO 5.1 but failed. Scheduler:ProcessTaskSchededuling sw:DocumentTimeManager::DoIdleJobs(Timer*) swViewShell::Layoutidle() SwLayIdle(swLayIdle (SwRootFrame* SwViewShellImp*) SwlayAction:Action (OutputDevice*)
I bibisected it with win32-5.0 to the same range you have in several bugs: commit 3f4cc8db52a676c8bb37ebcf9996e73ef3240f0d Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Mon May 25 22:26:52 2015 -0500 source 9b4abcd1c45a646a1ac9120fe1c489ba6bb44e95 source 9b4abcd1c45a646a1ac9120fe1c489ba6bb44e95 source acaafc03e623ac25d4408605f34d50618926c5d0 source 567f51192483059ec57c16a6045141746d4b01f9 source ef6f2490a697e7c23fea40c567f751db05f1bbbf source 2c0189a8a3aeb3668bf6de1ea1958ba475b80a38 source 3da65dc8982167517f19e80a288b049118bc3d23 source 2a0b6705724c4ea65b56eb0f45bccfa253d9fdc2 source 59619dbe971852d5cd35dcc3f78eda9bebeb99aa source e7c2b4b981b9b43c31fa442d5596b7a765dbe699 source 6f4dc6af39ecf2f90155205ad097601a8b2f602c source ca3700c42238e71684ec1d5f5eacaea4b1ca3b30 source 8da61f23384c7f3f2850a6362765506e4e078862 source d05a64df34fd143670cb939b72abfb32d6b714c7 source 01f406bc28f53acc5a2734af637aa8074a5d1813 source b6bb2e9315c9bc3338eaf066df40a969eb4774aa source d851e1e3c29afd3315cc763144c6eb92fbef5054 source 7e2a0df7e7b4551698d1d7172ef12ad1e0fd8826 source b11dba5be288ca5aaed1403093033708f7091c42 source 49439d4a67b06227e56a2855c856e3482323a28a source ff52f4e417eb4de5e85388a48a650429b1880762 source d411dca1ea6bfccb7090d4ceab15119253cac5bf source f384496d125255a94bfd5978e0cbe44d6d046adb source f33d6800fbdc42aa75477e31be0bba5a4a5a52c1 source 8f9b0c869222e57f738bc25d51cc6364e3c6a65a source 00717355c2d10bacbae46941b82247d74fd89108 source 2d95bc0510d43c11bb3bd03f590e24ba3d7ca30f source ddd4a787ebde1b47e5ddfbd5995e2a0fe6b22ee2 source 0e10b34342bd7b94b69f2eac8c9b1df89a2725f3 source b380220bc1404ed5a9daa1a28f70696e84543f61 source 5bd1106c3758c8cb0c19b09799970440501fde02 source 3f64e7c16a63fdc330e108cd74182c615d229bb6 source 4c3cea26b84cc70a67ff4eda99b842d8786a3628 source 256c5c3f28ef70b70d38e2e07dfca4baab654612 source 57656eb1fae5ae6c4d3b7542a385a93ff434e4e7 source 49524c6dcf04b9dadef8d2b084cf26abcf70b8a9 source 826143684d2697a8620373dce18fa5f24332d5cb source d8305248f687ffa522b56955508d82d60ad5b8c6 source a74efa665c8199899cd778900de686e2b8710fee source e6e8a060ecc6e4fd51cfe88e00d841d546ed5915 Same for: bug 113090 bug 115810 bug 113091 bug 119821 bug 120048 Some of those seem the same root issue, updating pagination or word count. So do you think it makes sense to keep this open?
This one & bug 120516 and bug 120048 are exactly the same, I think Bug 115810 maybe a dupe to, but feels slightly different I prefer these separated, for now. But could be the same root cause.. Bug 119821 Bug 120102 Bug 113091
Ok let's dupe this to the older one. Feel free to organise further. *** This bug has been marked as a duplicate of bug 120048 ***