I agree and have myself sometimes pondered about how to kill a context explicitly, and there's no way other than to release refs to all GL objects and leave it to the GC. It would be nice to have an explicit API, although the lose_context extension is not it (and shouldn't be), because it matches the resource loss semantics from the system, to solve another problem, and not the context itself. It would be nice to have a deleteContext() feature, since otherwise getContext()ing something effectively "taints" the <canvas> and ties it to that context type for its remaining lifetime, which is a bit messy. Not critical, but agree this is a bit dirty part if the API.
Unfortunately I have been unable to find the deleteContext function in the canvas API. Some implementations keep webGL contexts around even after all references are set to null. The WEBGL_lose_context extension seems to be the only way to declare you are finished with a context and free the context resource itself in a deterministic manor._____________
Ryan PattersonOn Fri, Nov 4, 2016 at 1:45 PM, Kenneth Russell <email@example.com> wrote:This deliberately isn't specified. If you're looking for a way to free your application's resources, you should use the various delete* APIs.-KenOn Fri, Nov 4, 2016 at 10:28 AM, <firstname.lastname@example.org> wrote:
It says the extension “WEBGL_lose_context” simulates webgl context loss. Does it mean the browser actually frees the resources on the GPU allocated by the webgl context or just pretends that it did?