RESOLVED WONTFIX 58306
compositing/webgl/webgl-nonpremultiplied-blend.html crashes on Mac OS X 10.6, Chromium DEBUG build
https://bugs.webkit.org/show_bug.cgi?id=58306
Summary compositing/webgl/webgl-nonpremultiplied-blend.html crashes on Mac OS X 10.6,...
Andrey Kosyakov
Reported 2011-04-12 01:48:08 PDT
compositing/webgl/webgl-nonpremultiplied-blend.html crashes on Mac OS X 10.6, Chromium DEBUG build Apparently, this started after r83552.
Attachments
Stack trace for crash (8.21 KB, text/plain)
2011-04-12 14:26 PDT, Kenneth Russell
no flags
Kenneth Russell
Comment 1 2011-04-12 13:32:35 PDT
This is reproducible. It seems necessary to reload the page and then wait a second. The following is printed to the console when the renderer crashes: ASSERTION FAILED: !m_deletionHasBegun ../../JavaScriptCore/wtf/RefCounted.h(37) : void WTF::RefCountedBase::ref() This is likely caused by the HashMap of RefPtrs to GraphicsContext3D instances.
John Bates
Comment 2 2011-04-12 14:21:14 PDT
(In reply to comment #1) > This is reproducible. It seems necessary to reload the page and then wait a second. The following is printed to the console when the renderer crashes: > > ASSERTION FAILED: !m_deletionHasBegun > ../../JavaScriptCore/wtf/RefCounted.h(37) : void WTF::RefCountedBase::ref() > > This is likely caused by the HashMap of RefPtrs to GraphicsContext3D instances. The crash does not seem to happen in Linux -- I tried lots of reloading, duplicating and closing the tab. Is it trivial for you to post the call stack from Mac?
Kenneth Russell
Comment 3 2011-04-12 14:25:47 PDT
Yes. I'll add it as an attachment since it's large.
Kenneth Russell
Comment 4 2011-04-12 14:26:34 PDT
Created attachment 89270 [details] Stack trace for crash
Andrey Kosyakov
Comment 5 2011-04-12 22:54:20 PDT
I'm also marking media/adopt-node-crash.html as CRASH with a reference to this bug, as it started crashing on GPU tests on Mac SL debug since about the same time: http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Mac10.6%20%28dbg%29/builds/481
Note You need to log in before you can comment on or make changes to this bug.