Bug 166969 - Noticeable lag while dragging a shape with a high resolution image in the background (Skia Raster)
Summary: Noticeable lag while dragging a shape with a high resolution image in the bac...
Status: RESOLVED DUPLICATE of bug 167002
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
25.8.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-12 15:02 UTC by Telesto
Modified: 2025-06-13 17:56 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2025-06-12 15:02:48 UTC 
Description:
Noticeable lag while dragging a shape with a high resolution image in the background (Skia Raster)

Steps to Reproduce:
1. Open attachment 201179 [details].
2. Insert a shape (say a smiley shape)
3. Select it and start moving the shape in circles

FWIW: this might be little less noticeable on new machines with a bit more single core performance



Actual Results:
Microstutters

Expected Results:
Smooth drag


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 25.8.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 17e8dbead42e2d4b55815b1b7b2846b03d62a15d
CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded
Comment 1 Telesto 2025-06-12 15:05:29 UTC 
Smooth with
Version: 25.2.2.0.0+ (X86_64) / LibreOffice Community
Build ID: d3c332aa2d721601b14ecfff3f4f83ab8e9cb5a5
CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded
Comment 2 Telesto 2025-06-12 17:32:58 UTC 
I have to re-check this; might be some user profile issue; or another factor involved
Comment 3 Telesto 2025-06-13 17:56:55 UTC 

*** This bug has been marked as a duplicate of bug 167002 ***