| Summary: | UI: Comment box starts flashing on keypress when in table causing lots of redundant paints (hammering the CPU) | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Telesto <telesto> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | trivial | CC: | 79045_79045, dgp-mail |
| Priority: | lowest | Keywords: | perf |
| Version: | 7.0.0.1 rc | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 106179 | ||
| Attachments: | Example file | ||
|
Description
Telesto
2021-09-23 15:23:37 UTC
Created attachment 175224 [details]
Example file
I confirm it with Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7cd5b35caa8d4fa9d0ba2b2c6ce4b88726ed2be6 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL but - to be honest - I've never seen a more trivial bug than this one. (In reply to Dieter from comment #2) > but - to be honest - I've never seen a more trivial bug than this one. Depends on the perspective :-). Lets give add some background (narrative/ spin). Some people might struggle with this; like people with epilepsy, strobe and visual motion sensitivity. MarjE (marching ants) Also flashing might mean lots of paint refreshes; which causes high CPU load. It's actually 7% for basic table & a comment in it while holding the key Pick some lovely big document and like attachment 121138 [details] (there is table with comment on page 1)... and CPU hammering at 25%. It's smooth, so you can say well nothing bad.. But well if you're on battery this less joyful (battery drain). And next I jump topic the environmental dimensions. A lots energy wasted. If you look at the individual scale this maybe, nah. But if you take into account all users this probably adds up. [Yes, even software could/should have an eco-label] 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 |