Closed
Bug 1169331
Opened 10 years ago
Closed 10 years ago
Text hugely stretched vertically during vert. scrolling of list
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
FIXED
mozilla41
| Tracking | Status | |
|---|---|---|
| firefox38 | --- | wontfix |
| firefox38.0.5 | - | wontfix |
| firefox39 | + | wontfix |
| firefox40 | --- | unaffected |
| firefox41 | --- | unaffected |
| firefox-esr31 | --- | unaffected |
| firefox-esr38 | 39+ | affected |
People
(Reporter: jim.avera, Assigned: mstange)
References
Details
(Whiteboard: [gfx-noted])
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150511103303
Steps to reproduce:
Visit https://www.mageia.org/en/about/2010-sept-announcement.html#people
and scroll through the list of people (there will be two scroll-bars: One for the whole page, which is very long, and a second "inner" scroll bar for the list of people).
Actual results:
While scrolling in the list, lines will suddenly elongate vertically to consume most of the list viewport, then collapse back to normal as the scroll progresses.
===> Please see the attached screen-shot
Expected results:
Lines should scroll by normally without being periodically blown up to huge height.
Update: The bug seems to occur only when you first start at the top of the page and then scroll down to the "People" section with the mouse wheel (not by manipulating the scroll bar directly). THEN grab the inner-most scroll bar to scroll the list of people, and the rendering problem happens.
Please start by visiting https://www.mageia.org/en/about/2010-sept-announcement.html
(without the #people id suffix given in the original post) and use the scroll-wheel to bring the "People" section into view.
Comment 2•10 years ago
|
||
[Tracking Requested - why for this release]: Rendering problem on ESR38 on Ubuntu14.04
Status: UNCONFIRMED → NEW
status-firefox38:
--- → affected
status-firefox38.0.5:
--- → affected
status-firefox39:
--- → affected
status-firefox-esr38:
--- → affected
tracking-firefox38.0.5:
--- → ?
tracking-firefox39:
--- → ?
tracking-firefox-esr38:
--- → ?
Component: Untriaged → Graphics
Ever confirmed: true
OS: Unspecified → Linux
Product: Firefox → Core
Comment 3•10 years ago
|
||
Graphics of the version with the defect
Graphics
--------
Adapter Description: VMware, Inc. -- Gallium 0.4 on SVGA3D; build: RELEASE;
Asynchronous Pan/Zoom: none
Device ID: Gallium 0.4 on SVGA3D; build: RELEASE;
Driver Version: 2.1 Mesa 10.1.3
GPU Accelerated Windows: 0/1 Basic (OMTC)
Supports Hardware H264 Decoding: false
Vendor ID: VMware, Inc.
WebGL Renderer: VMware, Inc. -- Gallium 0.4 on SVGA3D; build: RELEASE;
windowLayerManagerRemote: true
AzureCanvasBackend: cairo
AzureContentBackend: cairo
AzureFallbackCanvasBackend: none
AzureSkiaAccelerated: 0
status-firefox40:
--- → affected
status-firefox41:
--- → unaffected
status-firefox-esr31:
--- → unaffected
tracking-firefox40:
--- → ?
Updated•10 years ago
|
tracking-firefox40:
? → ---
Updated•10 years ago
|
Component: Graphics → Graphics: Layers
Comment 4•10 years ago
|
||
This have been broken since Firefox34 at least.
And was fixed in cycle of Nightly40.
Fixed range
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=4d6d69f0f499&tochange=d0fc7202b4cb
Comment 5•10 years ago
|
||
Markus, looks like one of your patches fixed the issue, do you think you could identify which part and if it is worth uplifting ?
Flags: needinfo?(mstange)
Whiteboard: [gfx-noted]
| Assignee | ||
Comment 6•10 years ago
|
||
All those patches need to land together, and they're way too risky to uplift. Moreover, this is not the kind of bug they should have fixed; they might have jiggled things around so that we don't hit the code path with the bug, so the real bug will probably still exist somewhere. (For example, those patches made us use opaque layers where we were using transparent layers before in some cases, and the reverse.)
I'll see whether I can reproduce the problem under rr (or whether it's an xrender bug).
Assignee: nobody → mstange
Status: NEW → ASSIGNED
Flags: needinfo?(mstange)
| Assignee | ||
Comment 7•10 years ago
|
||
This reproduces under rr. :-)
| Assignee | ||
Updated•10 years ago
|
Summary: Text hugely streached vertically during vert. scrolling of list → Text hugely stretched vertically during vert. scrolling of list
Comment 8•10 years ago
|
||
[Tracking Requested - why for this release]:
Clearly not a driver for a 38 dot releases.
If we have a safe patch, why not uplifting it to 39.
ESR sounds unlikely as we have this bug since Fx 34.
Comment 9•10 years ago
|
||
Tracked for 39. We're about to ship beta 3, but this could ship in beta 4, if you land a patch.
| Assignee | ||
Comment 10•10 years ago
|
||
(In reply to Alice0775 White from comment #3)
> Graphics of the version with the defect
>
> Graphics
> --------
>
> Adapter Description: VMware, Inc. -- Gallium 0.4 on SVGA3D; build: RELEASE;
> Asynchronous Pan/Zoom: none
> Device ID: Gallium 0.4 on SVGA3D; build: RELEASE;
> Driver Version: 2.1 Mesa 10.1.3
> GPU Accelerated Windows: 0/1 Basic (OMTC)
The OMTC part here confuses me. Alice, can you confirm that this bug is really reproducible in a build that uses OMTC? I've only been able to reproduce it without OMTC, and in most builds I've tried, setting layers.offmainthreadcomposition.enabled to true didn't even cause OMTC to be turned on.
Flags: needinfo?(alice0775)
| Assignee | ||
Comment 11•10 years ago
|
||
Bug 1169331 - Always clip rotated buffer quadrant drawing to the fill rect. r?jrmuizel
Attachment #8616139 -
Flags: review?(jmuizelaar)
Updated•10 years ago
|
Attachment #8616139 -
Flags: review?(jmuizelaar) → review+
Comment 12•10 years ago
|
||
(In reply to Markus Stange [:mstange] from comment #10)
> (In reply to Alice0775 White from comment #3)
> > Graphics of the version with the defect
> >
> > Graphics
> > --------
> >
> > Adapter Description: VMware, Inc. -- Gallium 0.4 on SVGA3D; build: RELEASE;
> > Asynchronous Pan/Zoom: none
> > Device ID: Gallium 0.4 on SVGA3D; build: RELEASE;
> > Driver Version: 2.1 Mesa 10.1.3
> > GPU Accelerated Windows: 0/1 Basic (OMTC)
>
> The OMTC part here confuses me. Alice, can you confirm that this bug is
> really reproducible in a build that uses OMTC? I've only been able to
> reproduce it without OMTC, and in most builds I've tried, setting
> layers.offmainthreadcomposition.enabled to true didn't even cause OMTC to be
> turned on.
My bad, reproduced w/o OMTC.
Flags: needinfo?(alice0775)
Comment 13•10 years ago
|
||
Markus is this ready to land ? Or are you still working on it? Thanks.
Flags: needinfo?(mstange)
| Assignee | ||
Comment 14•10 years ago
|
||
| Assignee | ||
Comment 15•10 years ago
|
||
Just need to wait for the tryserver results, then I'll land it.
Flags: needinfo?(mstange)
| Assignee | ||
Comment 16•10 years ago
|
||
Comment 17•10 years ago
|
||
Backed out for being the most-likely cause of semi-frequent Android debug reftest failures like the log shown below:
https://treeherder.mozilla.org/logviewer.html#?job_id=10679939&repo=mozilla-inbound
https://hg.mozilla.org/integration/mozilla-inbound/rev/99d6da0042f3
| Assignee | ||
Comment 18•10 years ago
|
||
| Assignee | ||
Comment 19•10 years ago
|
||
| Assignee | ||
Comment 20•10 years ago
|
||
Comment 21•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a490322a1877
https://hg.mozilla.org/mozilla-central/rev/b9562bd4954b
https://hg.mozilla.org/mozilla-central/rev/cf373ad45129
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
| Assignee | ||
Comment 22•10 years ago
|
||
Comment 23•10 years ago
|
||
Markus or Jeff, do you want to request uplift for this at least to aurora? May be a bit late for beta unless you think it is super important not to ship this with 39 and you can verify it works on nightly.
Flags: needinfo?(mstange)
Flags: needinfo?(jmuizelaar)
Comment 24•10 years ago
|
||
Comment 25•10 years ago
|
||
Just realized aurora is unaffected. Wontfix for 39 since at this point we are pretty focused on stability and security fixes.
You need to log in
before you can comment on or make changes to this bug.
Description
•