Closed
Bug 807741
Opened 12 years ago
Closed 12 years ago
Blacklist WebGL antialiasing on Mac on NVIDIA and Intel driver
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox-esr10 | 17+ | fixed |
firefox-esr17 | --- | fixed |
b2g18 | --- | unaffected |
People
(Reporter: bjacob, Assigned: bjacob)
References
Details
(Keywords: sec-high, Whiteboard: [adv-track-esr17-])
Attachments
(1 file, 1 obsolete file)
965 bytes,
patch
|
jgilbert
:
review+
akeybl
:
approval-mozilla-esr10+
|
Details | Diff | Splinter Review |
Thanks to our friends at Google for reporting this and making a testcase. http://code.google.com/p/chromium/issues/detail?id=137303 Testcase: http://www.khronos.org/registry/webgl/sdk/tests/conformance/rendering/multisample-corruption.html There is no alternative to blacklisting MSAA on Mac/NVIDIA until this is fixed. Apple Radar 12557679: Corruption of OpenGL Multisample Renderbuffers with NVIDIA chipsets
Assignee | ||
Updated•12 years ago
|
Whiteboard: sec-high
Assignee | ||
Comment 1•12 years ago
|
||
Doing this with a compiled blacklist as it's tedious to list all Mac OS versions in separate XML entries. Also with 17 we get an opportunity to deliver this to users rather soon.
Attachment #677498 -
Flags: review?(joe)
Comment 2•12 years ago
|
||
Comment on attachment 677498 [details] [diff] [review] patch Review of attachment 677498 [details] [diff] [review]: ----------------------------------------------------------------- ::: widget/cocoa/GfxInfo.mm @@ +328,5 @@ > (nsAString&) GfxDriverInfo::GetDeviceVendor(VendorATI), GfxDriverInfo::allDevices, > + nsIGfxInfo::FEATURE_WEBGL_MSAA, nsIGfxInfo::FEATURE_BLOCKED_DEVICE); > + IMPLEMENT_MAC_DRIVER_BLOCKLIST(DRIVER_OS_ALL, > + (nsAString&) GfxDriverInfo::GetDeviceVendor(VendorNVIDIA), GfxDriverInfo::allDevices, > + nsIGfxInfo::FEATURE_WEBGL_MSAA, nsIGfxInfo::FEATURE_BLOCKED_DEVICE); Add a comment referring to this bug.
Attachment #677498 -
Flags: review?(joe) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Now that sucks: Google has disclosed this bug publicly on public-webgl and also the Chromium bug seems publicly accessible: http://code.google.com/p/chromium/issues/detail?id=137303 Can this wait for Firefox 17 or do we want to deploy this on the downloadable blacklist?
Assignee | ||
Comment 4•12 years ago
|
||
Also, is there still a point in hiding this bug?
Assignee | ||
Comment 5•12 years ago
|
||
The Chromium bug seems to have morphed into NVIDIA + Intel. Joe: can you prepare the downloadable blacklist updates or teach me how to do that?
Summary: Blacklist WebGL antialiasing on Mac on NVIDIA driver → Blacklist WebGL antialiasing on Mac on NVIDIA and Intel driver
Comment 6•12 years ago
|
||
Getting a downloadable blacklist entry added is very easy. Simply file a bug like bug 806991, in that component, and specify what sections of the XML you want, and what you want them set to (literal strings). In this case it'll be all affected versions of OS X, so there will be several entries necessary. (eg Darwin 9, Darwin 10, Darwin 11, Darwin 12)
Comment 7•12 years ago
|
||
Thanks for rating it, but the rating is a keyword not a whiteboard entry. :)
Keywords: sec-high
Whiteboard: sec-high
Assignee | ||
Comment 8•12 years ago
|
||
Thanks Joe for the great documentation and ready-to-use bug request link. Filed bug 809550.
Comment 9•12 years ago
|
||
Is the patch here the right path forward for ESR10 (given bug 809550, and our inability to remote block in FF10)? We're going to build after Wednesday, so we'd need this to land asap.
tracking-firefox-esr10:
--- → ?
Assignee | ||
Comment 10•12 years ago
|
||
No, but _this_ patch is it. On try: https://tbpl.mozilla.org/?tree=Try&rev=cee5ddc245fb
Attachment #677498 -
Attachment is obsolete: true
Attachment #680677 -
Flags: review?(jgilbert)
Updated•12 years ago
|
Updated•12 years ago
|
Attachment #680677 -
Flags: review?(jgilbert)
Attachment #680677 -
Flags: review+
Attachment #680677 -
Flags: approval-mozilla-esr10?
Assignee | ||
Comment 11•12 years ago
|
||
Given the timeframe, please land this patch when you approve it. Try looks red, but it's unrelated. I seem to remember that pushing ESR10 to Try doesn't work anymore anyways.
Updated•12 years ago
|
Attachment #680677 -
Flags: approval-mozilla-esr10? → approval-mozilla-esr10+
Comment 12•12 years ago
|
||
(In reply to Benoit Jacob [:bjacob] from comment #11) > Given the timeframe, please land this patch when you approve it. You've got all of today and tomorrow to land - we don't land on behalf of engineers because we don't have the expertise to investigate/resolve tree bustage.
Assignee | ||
Comment 13•12 years ago
|
||
OK! I misunderstood, I thought that this had to land yesterday. https://hg.mozilla.org/releases/mozilla-esr10/rev/d5505b3df3c3
Assignee | ||
Comment 14•12 years ago
|
||
Also, this bug is FIXED by 809550.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Whiteboard: [adv-track-esr17-]
Updated•12 years ago
|
status-firefox-esr17:
--- → fixed
Updated•11 years ago
|
status-b2g18:
--- → unaffected
Updated•9 years ago
|
Group: core-security → core-security-release
Updated•8 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•