Bug 98204
| Summary: | Make sure WebGL is cleaning up shader source entries | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dean Jackson <dino> |
| Component: | WebGL | Assignee: | Dean Jackson <dino> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bfulgham, jonlee, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=137689 | ||
Dean Jackson
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/12416650>
Brent Fulgham
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.