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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 9 13:58:41 PDT 2012


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





--- Comment #13 from Kenneth Russell <kbr at google.com>  2012-05-09 13:57:46 PST ---
(In reply to comment #12)
]> 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?

I think the issue is more that the lifetime of the Frame may differ from that of the Document. My understanding is that if WebGLRenderingContext were an ActiveDOMObject and the page were destroyed, the WebGLRenderingContext would still be lost, even if the Canvas had been moved to a document that was still alive. This is a rare enough situation that the improvements in resource consumption should far outweigh the pitfalls in this scenario.

-- 
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