Open
Bug 1216797
Opened 10 years ago
Updated 3 years ago
Rendering issues on Travis build summary pages
Categories
(Core :: Graphics, defect)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox44 | --- | affected |
People
(Reporter: marco, Unassigned)
Details
(Whiteboard: gfx-noted)
Attachments
(4 files)
There are all kinds of rendering issues on Travis build status pages. For example, sometimes the entire tab bar becomes black.
Could you please attach a screenshot and steps to reproduce including any publicly accessible URLs? Are you seeing something similar to bug 1216210?
| Reporter | ||
Comment 2•10 years ago
|
||
To reproduce, simply open a Travis build status page (e.g. https://travis-ci.org/mozilla/oghliner/builds/86511272).
I can't always reproduce, I'll post a screenshot once I reproduce again (there are often flashing areas, so I can't always easily take screenshots).
The rendering issues I'm seeing look different from the screenshot in bug 1216210.
Thanks Marco, if you could, please also provide a copy of your about:support page.
| Reporter | ||
Comment 4•10 years ago
|
||
One of the issues that can be easily reproduced:
1) Open https://travis-ci.org/mozilla/oghliner/builds/86507975 (or another build status page)
2) While the page is loading, scroll up and down
3) See the loading throbber in the tab bar intermittently appear and disappear.
| Reporter | ||
Comment 5•10 years ago
|
||
Thanks, I cannot reproduce this locally on my Macbook Pro so maybe this is a Linux-only bug. I did notice several errors in your about:support#Graphics section:
(#0) Error: Failed to allocate a surface due to invalid size Size(0,0)
(#14) Error: Failed to allocate a surface due to invalid size Size(0,0)
(#15) Error: Failed to allocate a surface due to invalid size Size(0,0)
(#16) Error: Failed to allocate a surface due to invalid size Size(0,0)
(#17) Error: Failed to allocate a surface due to invalid size Size(0,0)
(#18) Error: Failed to allocate a surface due to invalid size Size(0,0)
Could you try running this on a new profile?
| Reporter | ||
Comment 7•10 years ago
|
||
I can reproduce in a clean profile as well.
| Reporter | ||
Comment 8•10 years ago
|
||
| Reporter | ||
Comment 9•10 years ago
|
||
| Reporter | ||
Comment 10•10 years ago
|
||
Comment 11•10 years ago
|
||
Thanks Marco. Did this start to happen recently? If so could you find a regression window using http://mozilla.github.io/mozregression/?
Milan, do the errors in comment 6 provide any leads?
Flags: needinfo?(milan)
Whiteboard: [gfx-note]
| Reporter | ||
Comment 12•10 years ago
|
||
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #11)
> Thanks Marco. Did this start to happen recently? If so could you find a
> regression window using http://mozilla.github.io/mozregression/?
I've been seeing rendering issues in general on Travis for quite some time now, I regret not having filed a bug before.
The throbber issue is more recent and easier to reproduce though, so I can probably find a regression window for it.
Comment 13•10 years ago
|
||
Nothing particularly sinister about comment 6 errors. Let's see where the regression range takes us.
Flags: needinfo?(milan)
| Reporter | ||
Comment 14•10 years ago
|
||
Comment 15•10 years ago
|
||
Related to GTK3 maybe?
Flags: needinfo?(karlt)
Whiteboard: [gfx-note] → gfx-noted
Comment 16•10 years ago
|
||
(In reply to Jeff Gilbert [:jgilbert] from comment #15)
> Related to GTK3 maybe?
Maybe. I can only guess, but the problems look more like graphics problems than problems in drawing of native gtk widgets. The urlbar glitch for example includes the back button.
The lines missing from "Build Jobs text/icons suggest perhaps off-by-one errors in display item dimensions. I wonder whether high dpi scaling is involved here somehow? The back button and search icons look larger than expected but not large enough for GDK's scaling factor of 2.
Flags: needinfo?(karlt)
| Reporter | ||
Comment 17•10 years ago
|
||
The resolution of the monitor was 1920x1080p.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•