Closed Bug 1285243 Opened 9 years ago Closed 9 years ago

Latest nightly is unusable on linux

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
Unspecified
Linux
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox50 + fixed

People

(Reporter: Usul, Assigned: jrmuizel)

References

Details

(Keywords: nightly-community, regression, Whiteboard: [mozfr-community])

scrolling procuding procuces gfx glitcehs entreing text produces glitches the load url is glicthy.
Keywords: nightly-community, regressionwindow-wanted
Whiteboard: [mozfr-community]
OS: Unspecified → Linux
Summary: Latest nighly is unusbale on linux → Latest nighly is unusable on linux
I can confirm today's build has tons of graphic problems on Ubuntu 16.04, Ludovic is on Fedora 24 and another user using Debian Sid also confirmed the problem on the #nightly IRC channel
Accélération graphique Fonctionnalités Composition Basic Zoom/Panoramique asynchrones entrée molette activée; entrée tactile activée Rendu WebGL Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell Mobile Décodage matériel H264 No GPU 1 Actif Oui Description Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell Mobile ID du vendeur Intel Open Source Technology Center ID du périphérique Mesa DRI Intel(R) Haswell Mobile Version du pilote 3.0 Mesa 11.2.2 (git-5de088f) Diagnostics AzureCanvasAccelerated 0 AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend none CairoUseXRender 0 Journal des décisions HW_COMPOSITING blocked by default: Acceleration blocked by platform OPENGL_COMPOSITING unavailable by default: Hardware compositing is disabled
Summary: Latest nighly is unusable on linux → Latest nightly is unusable on linux
Narrowed inbound regression window from [320ee111, cc866385] (3 revisions) to [3ead61d6, cc866385] (2 revisions) (~1 t)INes, no (more) inbound revisions :(INFO: Last good revision: 3ead61d6add69268a1a240a9bc36891b9e3b763aINFO: First bad revision: cc866385dd0124bde69f1d7fd50baee93c531ddf Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3ead61d6add69268a1a240a9bc36891b9e3b763a&tochange=cc866385dd0124bde69f1d7fd50baee93c531ddf Looks like the following bug has the changes which introduced the regression: https://bugzilla.mozilla.org/show_bug.cgi?id=1284808
Keywords: regressionwindow-wanted
The regression window identified by mozregression points at bug 1284808 as the likely bug that introduced the regression but the regression window also has bug 1284440 listed and thjs a graphics change so maybe this is this one instead.
Problems go away with layers.acceleration.force-enabled;true Apart of missing highlight background of bookmark lists when the list is long enough (only first 3-4 entries show the highlight when hovering over), don't know if this is the same Bug (but new in todays nightly).
[Tracking Requested - why for this release]: I can reproduce on Nightly50.0a1 on Ubuntu14.04. Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3ead61d6add69268a1a240a9bc36891b9e3b763a&tochange=c8700e65f41b9a7ead1047848e06d1eddd62564d Regressed by: c8700e65f41b Morris Tseng — Bug 1284440 - Prevent CreateRenderTargetForWindow from clearing unwanted area. r=mattwoodrow
Blocks: 1284440
tracking-firefox50: --- → ?
Flags: needinfo?(mtseng)
Flags: needinfo?(matt.woodrow)
This is also affected to the Profile Manager. STR 1. Create many user profiles(more than 6) 2. firefox -no-remote -P 3. Try to scroll the profile list Actual Results: The listbox would not scroll and become glitch
Tracking 50+ for this Linux regression.
tracking-firefox50: ? → +
Assignee: nobody → jmuizelaar
This offending change has been backed out. New nightlies will be spun.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
I saw this problem in ubuntu 16.04 today and workaround in comment 5 helped me. After the latest nightly from later today (navigator.buildID is now "20160707083343") I was able to undo the workaround and still have this nightly work fine. So I can confirm the fix
Flags: needinfo?(mtseng)
Flags: needinfo?(matt.woodrow)
You need to log in before you can comment on or make changes to this bug.