Bug 125807 - Visual artifacts with specific document when scrolling
Summary: Visual artifacts with specific document when scrolling
Status: VERIFIED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
: 125900 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-06-09 01:33 UTC by Mike Kaganski
Modified: 2019-06-13 17:26 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
A document which gives visual artifacts when scrolled (258.50 KB, application/msword)
2019-06-09 01:33 UTC, Mike Kaganski
Details
clip of the visual corruption of the page canvas (72.18 KB, image/png)
2019-06-09 13:50 UTC, V Stuart Foote
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2019-06-09 01:33:08 UTC
Created attachment 152059 [details]
A document which gives visual artifacts when scrolled

Trying to scroll down and up the document gives visual artifacts.

On the screencast https://youtu.be/ZYyxc2Ql96U, it's visible e.g. that the page break does not go outside the visible area, despite it should (note the scrollbar movement); scrollong down, resizing window, then scrolling up makes more glitches.

Tested with Version: 6.4.0.0.alpha0+ (x64)
Build ID: fe977ec07087b103de8c809597fdaea8dd629837
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

OS UI scaling is 150%.
Comment 1 V Stuart Foote 2019-06-09 13:48:07 UTC
Confirming on Windows 10 Home 64-bit en-US (1809) with Intel HD Graphics 620 (driver 25.20.100.6519) and
Version: 6.4.0.0.alpha0+ (x86)
Build ID: 9870ff897f088563426bee9567dd9cb722c2b929
CPU threads: 4; OS: Windows 10.0; UI render: GL (or default); VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded

Affecting both default and OpenGL rendering. Position of the page break after the frame holding the list of bell ringers, which is very close to the bottom margin, looks to be miscalculated when scrolling. Key to STR is to zoom in or out resizing  portion of document on screen, and then start to scroll. 

Attaching a clip.

Same system, but could not reproduce with
Version: 6.2.4.2 (x64)
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU threads: 4; OS: Windows 10.0; UI render: GL (or default); VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Comment 2 V Stuart Foote 2019-06-09 13:50:09 UTC
Created attachment 152063 [details]
clip of the visual corruption of the page canvas
Comment 3 V Stuart Foote 2019-06-09 13:52:29 UTC
Comment on attachment 152063 [details]
clip of the visual corruption of the page canvas

had set a color for the frame so its extent is visible during scroll
Comment 4 Xisco Faulí 2019-06-11 09:29:35 UTC
@V Stuart Foote, if you can reproduce it in 6.4 but not in 6.2 please do not forget to add the regression keyword...
Comment 5 Xisco Faulí 2019-06-11 09:37:54 UTC
Regression introduced by:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=a46a257794f1f53b294735fc876c394be23a3811

author	Noel Grandin <noel.grandin@collabora.co.uk>	2019-06-05 15:24:04 +0200
committer	Noel Grandin <noel.grandin@collabora.co.uk>	2019-06-07 11:01:37 +0200
commit a46a257794f1f53b294735fc876c394be23a3811 (patch)
tree 9eb4fb72df2cc9e2acdf3edffe0a72f67f90b9fa
parent 43ddddb703bcdb9430752af63ae46527f737f874 (diff)
improve empty tools::Rectangle (width)

Bisected with: bibisect-linux64-6.4

Adding Cc: to Noel Grandin
Comment 6 Noel Grandin 2019-06-12 10:12:25 UTC
The problematic commit has been reverted
Comment 7 Xisco Faulí 2019-06-13 10:15:58 UTC
Verified in

Version: 6.4.0.0.alpha0+
Build ID: ee4823e16e5fece068ee123b9c3e29834cd38763
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded
Comment 8 Jacques Guilleron 2019-06-13 17:26:18 UTC
*** Bug 125900 has been marked as a duplicate of this bug. ***