Bug 98204 - Make sure WebGL is cleaning up shader source entries
Summary: Make sure WebGL is cleaning up shader source entries
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebGL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Dean Jackson
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2012-10-02 15:00 PDT by Dean Jackson
Modified: 2017-09-11 22:55 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Jackson 2012-10-02 15:00:02 PDT 
It's not clear to me that GraphicsContext3D is doing what it can to delete entries from its shader source map (and variable info map) after a shader and it's program are deleted.
Comment 1 Radar WebKit Bug Importer 2012-10-02 15:00:50 PDT 
<rdar://problem/12416650>
Comment 2 Brent Fulgham 2014-01-10 12:53:42 PST 
When we call ::glDeleteShader, if the shader is still linked to a program it gets marked for deletion, not immediately destroyed.

Do we need to hold onto our shader source entries until the actual shader object is cleaned up by OpenGL?

There doesn't seem to be API to be notified when the deletion actually occurs.