I would just like to emphasize, as the wiki page you linked to
explains, that you can test lost context events by using the
WEBGL_lose_context extension (currently with WEBKIT_ and MOZ_ vendor
prefixes).
FWIW, we have definite plans to start generating context losses in
more cases than we currently do. Currently, aside from the
lose_context extension, you only get a WebGL context loss when the
underlying OpenGL context is lost (either through the ARB_robustness
watchdog timer, or EGL_CONTEXT_LOST on mobile devices). We ( =
Mozilla) plan to lose contexts in increasingly many cases:
- when a given page creates too many WebGL contexts (where too many
it at least 8), we'll probably start losing the least recently used
context.
- in the farther future, we could well start losing WebGL contexts of
tabs that have been inactive for a long time, as part of a more
general effort to reduce memory usage for users who have many
(sometimes: hundreds) of inactive tabs.
So, handling lost contexts will become increasingly important.
Benoit
2012/3/31 Lindsay Kay <lindsays...@gmail.com>:
You will need to explicitly restore all state.Benoit
2012/4/1 Rehno Lindeque: