Bug 534914 - Possible regression in gradient rendering for very large diagrams
Summary: Possible regression in gradient rendering for very large diagrams
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-05-21 08:52 EDT by Pierre-Charles David CLA
Modified: 2018-10-26 11:25 EDT (History)
1 user (show)

See Also:

Attachments
Broken gradient rendering starting at around X=16.5k (48.93 KB, image/png)
2018-05-21 08:52 EDT, Pierre-Charles David CLA 		no flags Details
Gradient rendering even more broken further to the right (X=65k) (48.12 KB, image/png)
2018-05-21 08:53 EDT, Pierre-Charles David CLA 		no flags Details
View All 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 Pierre-Charles David CLA 2018-05-21 08:52:46 EDT 
Created attachment 274116 [details]
Broken gradient rendering starting at around X=16.5k

I'm testing a very large (especially wide) diagram under Linux using Sirius 6.0M7 and a Photon Staging (e.g. Photon M7) target platform, and noticed that starting from about 16.5k pixels right of the origin, the rendering of the gradients in the diagram elements is broken.

Going even further to the right, it's worse and worse: around X=65k, each container in the diagram has several multiple gradient bands (around 4) instead of 1 single version of the gradient filling the shape.

It smells like a rounding error issue. I'm marking this as "possible regression", but it may have been like this forever, this kind of huge diagrams are not that common.
Comment 1 Pierre-Charles David CLA 2018-05-21 08:53:31 EDT 
Created attachment 274117 [details]
Gradient rendering even more broken further to the right (X=65k)
Comment 2 Florian Barbin CLA 2018-10-26 11:25:18 EDT 
I have also reproduced this issue on my gnome environment.