GetGraphicsResetStatusEXT returns only UNKNOWN

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Cause a context loss by DoSing an ANGLE context.
2. Call GetGraphicsResetStatusEXT().
3. Observed value is UNKNOWN.

What is the expected output? What do you see instead?
Expects GUILTY or INNOCENT.

What version of the product are you using? On what operating system?
r885, Windows

Please provide any additional information below.

Original issue reported on code.google.com by d...@sherk.me on 6 Dec 2011 at 12:38

[GoogleCodeExporter]

This is essentially the expected behavior. It seems unlikely that it will be 
possible to provide finer grained information about guilty or innocent contexts 
on top of D3D's device loss error codes. apatrick had a suggestion that 
specifically testing for D3DERR_DEVICEHUNG may allow detection of the device 
guilty of provoking the reset; this should be tested.

Original comment by kbr@chromium.org on 6 Dec 2011 at 1:03

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Yes, as Ken stated,  this is the intended behaviour.  I don't believe the 
DEVICEHUNG error will be useful as it will not allow us to determine which GL 
context caused the problem -- just that one of the contexts may have caused a 
problem.  (This is because all the GL contexts share the same D3D device).

Original comment by dan...@transgaming.com on 6 Dec 2011 at 3:45

[GoogleCodeExporter]

Original comment by c...@chromium.org on 7 Dec 2013 at 4:07

[GoogleCodeExporter]

Original comment by geofflang@chromium.org on 10 Dec 2013 at 3:50

[GoogleCodeExporter]

Works as intended.

Original comment by c...@chromium.org on 31 Jan 2014 at 8:14

• Changed state: Invalid