Closed
Bug 1179280
Opened 9 years ago
Closed 9 years ago
Update ANGLE from chromium/2214 to chromium/2466
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
FIXED
mozilla44
Tracking | Status | |
---|---|---|
firefox43 | --- | unaffected |
firefox44 | --- | fixed |
People
(Reporter: milan, Assigned: jrmuizel)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
Make sure we touch README.mozilla so that we can track what version we're on.
Reporter | ||
Updated•9 years ago
|
OS: Unspecified → All
Reporter | ||
Comment 1•9 years ago
|
||
I don't really want to wait for our patches to get uplifted, but lets see how the timing goes. If we do have local patches, I'd like the landing of this to be in a three part patch set - the first one to undo our changes and get angle back to what it was in 2214; the second to just update to 2403; the third one to add our changes on top.
Reporter | ||
Comment 2•9 years ago
|
||
We should also investigate the flags ANGLE has and see if we're doing the right thing.
Component: Graphics → Canvas: WebGL
Reporter | ||
Comment 3•9 years ago
|
||
Stuff in WebGLShaderValidator.cpp, ChooseValidatorCompileOptions function.
Comment 4•9 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #2) > We should also investigate the flags ANGLE has and see if we're doing the > right thing. I did do this in the past (maybe when I did the WebGLShaderValidator code), and cross-compared what we do with WRT Chromium.
Assignee | ||
Comment 5•9 years ago
|
||
WIP in https://github.com/jrmuizel/angle/tree/minimal-changes-on-chrome-2466
Reporter | ||
Updated•9 years ago
|
Assignee: nobody → jmuizelaar
Assignee | ||
Updated•9 years ago
|
Summary: Update ANGLE from chromium/2214 to chromium/2403 → Update ANGLE from chromium/2214 to chromium/2466
Assignee | ||
Comment 6•9 years ago
|
||
Try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=d9cbb41bacba
Assignee | ||
Updated•9 years ago
|
Comment 8•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/56db457aef33
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox44:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla44
Comment 9•9 years ago
|
||
There is a performance impact observed after this update, marked down as https://bugzilla.mozilla.org/show_bug.cgi?id=1210683.
Assignee | ||
Comment 11•9 years ago
|
||
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #10) > Marking affected for 43. That doesn't make sense to me. This didn't land until 44.
Flags: needinfo?(lhenry)
Comment 12•9 years ago
|
||
I'll find you on irc, there was a reference to this from another bug.
Flags: needinfo?(lhenry)
Comment 13•9 years ago
|
||
I misunderstood, thanks for the explanation Jeff!
Updated•8 years ago
|
Blocks: CVE-2016-1944
You need to log in
before you can comment on or make changes to this bug.
Description
•