New issue
Advanced search Search tips

Issue 779204 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
danakj@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

SharedGpuContext should use the context loss callback mechanism

Project Member Reported by junov@chromium.org, Oct 27 2017 
The implementation of SharedGpuContext currently relies on polling to determine whether its context was lost.  It should instead register a callback.  This would allow stale contexts to be detected earlier.

Comment 1 by danakj@chromium.org, Oct 27 2017 

Note that if you make an error and flush() that asking for an error will show it exists immediately, while the callback won't run until leaving the callstack. This came up in some canvas context lost tests before. Just in case you bump into this.

I am currently mucking in SharedGpuContext also, but to make it ask about gpu compositing on the main thread when making a context (very similar to what i was trying in https://chromium-review.googlesource.com/c/chromium/src/+/703979)

Comment 2 by junov@chromium.org, Jul 25

Owner: ----
Status: Available (was: Assigned)
►

Sign in to add a comment