[Webkit-unassigned] [Bug 76225] Release WebGL contexts eagerly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 9 00:11:29 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=76225





--- Comment #12 from yongsheng <yongsheng.zhu at intel.com>  2012-05-09 00:10:23 PST ---
(In reply to comment #11)
> crogers and abarth pointed out that making WebGLRenderingContext an ActiveDOMObject would give it the desired semantics, or at least something very close to the desired semantics. abarth's high level point is that ContextDestructionObserver (which ActiveDOMObject subclasses) is good for shutting down things that are tied to the Document, where FrameDestructionObserver is good for shutting down things tied to the lifetime of the surrounding Frame. Since the WebGLRenderingContext is tied to the Canvas which is tied to the Document, it matches ActiveDOMObject more closely.

Is this because FrameDestructionObserver will be notified once the page is destroyed, but ContextDestructionObserver won't be notified? So WebGLRenderingContext could be reused later as described below?

Frame Destruction is done once the page is destroyed, what about document destruction?

> 
> For correctness, we could just have the WebGLRenderingContext force a context lost event when the page is destroyed. That way if the canvas is still reachable from JavaScript after the document has been destroyed (for example, transplanted from one page to another) it can continue to work in the new page.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list