RESOLVED FIXED Bug 59045
Check for null m_context in WebGLLayerChromium and add resetting platform layer's context in the destructor of GraphicsContext3D.
https://bugs.webkit.org/show_bug.cgi?id=59045
Summary Check for null m_context in WebGLLayerChromium and add resetting platform lay...
Alexey Marinichev
Reported 2011-04-20 17:17:18 PDT
Check for null m_context in WebGLLayerChromium and add resetting platform layer's context in the destructor of GraphicsContext3D.
Attachments
Patch (4.37 KB, patch)
2011-04-20 17:20 PDT, Alexey Marinichev
no flags
Patch (4.37 KB, patch)
2011-04-20 17:53 PDT, Alexey Marinichev
no flags
Patch (4.52 KB, patch)
2011-04-20 18:00 PDT, Alexey Marinichev
no flags
Alexey Marinichev
Comment 1 2011-04-20 17:20:33 PDT
Alexey Marinichev
Comment 2 2011-04-20 17:23:13 PDT
This is to avoid dereferencing stale pointer when recovering from lost context.
Kenneth Russell
Comment 3 2011-04-20 17:37:31 PDT
Comment on attachment 90454 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=90454&action=review The code change looks good. We've talked offline about the fact that it's only feasible to test this in an automated fashion with a Chromium browser test, which is being worked on. Unfortunately there's a problem with the ChangeLog that needs to be fixed. > Source/WebCore/ChangeLog:8 > + No new tests. (OOPS!) The commit queue will reject this patch because of the presence of this line. You'll need to update it with information about the testing status.
Alexey Marinichev
Comment 4 2011-04-20 17:53:19 PDT
Alexey Marinichev
Comment 5 2011-04-20 18:00:05 PDT
Kenneth Russell
Comment 6 2011-04-20 18:09:48 PDT
Comment on attachment 90462 [details] Patch Looks good. r=me
WebKit Commit Bot
Comment 7 2011-04-20 18:38:27 PDT
Comment on attachment 90462 [details] Patch Clearing flags on attachment: 90462 Committed r84449: <http://trac.webkit.org/changeset/84449>
WebKit Commit Bot
Comment 8 2011-04-20 18:38:32 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.