Last Comment Bug 703487 - Implement ARB_robustness in WGL
: Implement ARB_robustness in WGL
Product: Core
Classification: Components
Component: Canvas: WebGL (show other bugs)
: Trunk
: All All
: -- normal (vote)
: mozilla11
Assigned To: Doug Sherk (:drs) (inactive)
Depends on:
Blocks: 707860 656824 711579
  Show dependency treegraph
Reported: 2011-11-17 19:03 PST by Doug Sherk (:drs) (inactive)
Modified: 2011-12-16 12:48 PST (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Patch v1.0, WGL implementation of ARB_robustness. (10.26 KB, patch)
2011-11-18 22:34 PST, Doug Sherk (:drs) (inactive)
jacob.benoit.1: review+
Details | Diff | Review

Description Doug Sherk (:drs) (inactive) 2011-11-17 19:03:44 PST
Another low-hanging fruit of ARB_robustness. GLX is already done, which provides 90% of the framework for this. WGL has its own ARB_robustness extension which we need to load and handle correctly. There should be no work here outside thebes.
Comment 1 Doug Sherk (:drs) (inactive) 2011-11-18 22:34:42 PST
Created attachment 575625 [details] [diff] [review]
Patch v1.0, WGL implementation of ARB_robustness.

This is being activated completely fine and all the infrastructure to support it seems to work correctly (i.e. the stuff that was written for GLX ARB_robustness), but creating a robust context on WGL seems to do nothing on my machine; i.e. if I DoS the GPU it crashes the same as if it wasn't enabled. Perhaps my machine just doesn't properly support it, or the drivers state that they do but actually don't.
Comment 2 Doug Sherk (:drs) (inactive) 2011-11-18 22:37:31 PST
Try push:

Not sure what's up with the failed Android build. This should have no impact on Android so I'm not too worried about it. Almost every other try build today is getting that same red/burn.
Comment 3 Doug Sherk (:drs) (inactive) 2011-12-02 23:55:06 PST
Comment 4 Marco Bonardo [::mak] 2011-12-03 03:30:37 PST
the checkin comment has the wrong bug number

Note You need to log in before you can comment on or make changes to this bug.