Closed
Bug 1422907
Opened 8 years ago
Closed 8 years ago
Content not rendering in debug builds
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jld, Unassigned)
Details
Attachments
(2 files)
ff-debug-glitch.png
In debug builds of mozilla-central, and only debug builds, content mostly doesn't render (see attached screenshot of the stock newtab page), or renders incorrectly. This includes browser chrome like the tab bar.
Mousing over elements (e.g., the buttons in about:support) seems to work more reliably for getting them to at least partially show up.
I tried disabling sandboxing, and a few other things, but the only thing that seems to affect it is --enable-debug; otherwise it works normally. This is using `./mach run`, so it's definitely a clean profile.
I'll attach the about:support separately, because it looks like I can't do multiple attachments while filing a bug.
|
Reporter | |
Comment 1•8 years ago
|
||
|
||
Comment 2•8 years ago
|
||
Can you use hg bisect to pinpoint a regression?
|
|
Reporter | |
Comment 3•8 years ago
|
||
Finding a “good” revision might be hard: this also reproduces in a revision from 2017-11-12[*]. The “regression” is probably from upgrading the OS on this machine (Debian unstable), including the GPU drivers but also various system libraries.
[*] https://github.com/mozilla/gecko-dev/commit/177a5a8bdc6f94cc57f37aeb20608d3886bac1f7
|
|
Reporter | |
Comment 4•8 years ago
|
||
The revision that created 58.0a1 also has this bug, and the revision that created 57.0a1 doesn't even build anymore (bug 1423684). So, to answer the question asked in comment #2: No.
However, a mozilla-central debug build I downloaded from Treeherder doesn't reproduce this. So I'm going to try a few things to “bisect” the build environment.
Flags: needinfo?(jld)
|
|
Reporter | |
Comment 5•8 years ago
|
||
It didn't reproduce locally when building with GCC 6.4.0 (the version that seems to be used in CI.) It also doesn't reproduce with GCC 7.2.1, which Debian uploaded to unstable yesterday (7.2.0-17 vs. 7.2.0-16, in Debian's versioning[*]). So this is looking like a compiler bug that's now fixed, and in any case I can no longer reproduce it.
[*] http://metadata.ftp-master.debian.org/changelogs/main/g/gcc-7/gcc-7_7.2.0-17_changelog
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jld)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•