46163 2010-09-20 21:58:21 -0700 media/video-controls-with-mutation-event-handler.html is crashing on GTK and Chromium 2010-09-22 00:37:39 -0700 1 1 1 Unclassified WebKit Media 528+ (Nightly build) PC OS X 10.5 RESOLVED DUPLICATE 46169 P2 Normal --- 1 atwilson webkit-unassigned darin eric.carlson jamesr mrobinson pnormand oldest_to_newest 282091 0 atwilson 2010-09-20 21:58:21 -0700 This test is crashing on the GTK build: http://build.webkit.org/builders/GTK%20Linux%2032-bit%20Debug/builds/10225/steps/layout-test/logs/stdio It also happens on the chromium builds. Here's the backtrace I'm seeing on the chromium build bots (I think - I'm not 100% sure if this is up-to-date or an old stack trace): ASSERTION FAILED: !m_adoptionIsRequired (third_party/WebKit/WebCore/platform/TreeShared.h:63 void WebCore::TreeShared<T>::ref() [with T = WebCore::ContainerNode]) StackTrace::StackTrace() [0x81a182e] base::(anonymous namespace)::StackDumpSignalHandler() [0x8161f04] 0x4001c420 WebCore::Node::refEventTarget() [0x88adb30] WebCore::EventTarget::ref() [0x87a8cb4] WTF::refIfNotNull<>() [0x87aa90d] WTF::RefPtr<>::RefPtr() [0x89036fc] WebCore::Node::dispatchEvent() [0x89121ed] WebCore::Node::dispatchSubtreeModifiedEvent() [0x8913af1] WebCore::NamedNodeMap::addAttribute() [0x890c64d] WebCore::Element::setAttribute() [0x88fa45f] WebCore::Element::setAttribute() [0x88fa768] WebCore::HTMLInputElement::setType() [0x89ece1d] WebCore::MediaControlInputElement::MediaControlInputElement() [0x8dffa14] WebCore::MediaControlRewindButtonElement::MediaControlRewindButtonElement() [0x8e01ee4] WebCore::MediaControlRewindButtonElement::create() [0x8dffd87] WebCore::RenderMedia::createRewindButton() [0x8c606fd] WebCore::RenderMedia::updateControls() [0x8c60dd6] WebCore::RenderMedia::updateFromElement() [0x8c6139b] WebCore::RenderVideo::updateFromElement() [0x8cacca9] WebCore::HTMLMediaElement::attach() [0x89fba85] WebCore::HTMLVideoElement::attach() [0x8a17658] WebCore::ContainerNode::attach() [0x88b4473] WebCore::Element::attach() [0x88f8e32] WebCore::Element::recalcStyle() [0x88f87a3] WebCore::Element::recalcStyle() [0x88f8d4a] WebCore::Element::recalcStyle() [0x88f8d4a] WebCore::Document::recalcStyle() [0x88c906f] WebCore::Document::updateStyleIfNeeded() [0x88c8d41] WebCore::Document::implicitClose() [0x88c8346] WebCore::FrameLoader::checkCallImplicitClose() [0x8af853e] WebCore::FrameLoader::checkCompleted() [0x8afb26a] WebCore::FrameLoader::finishedParsing() [0x8afb44d] WebCore::Document::finishedParsing() [0x88c7046] WebCore::HTMLTreeBuilder::finished() [0x8a64dab] WebCore::HTMLDocumentParser::end() [0x8a44976] WebCore::HTMLDocumentParser::attemptToRunDeferredScriptsAndEnd() [0x8a44a63] WebCore::HTMLDocumentParser::prepareToStopParsing() [0x8a4560f] WebCore::HTMLDocumentParser::attemptToEnd() [0x8a44895] WebCore::HTMLDocumentParser::finish() [0x8a448cb] WebCore::Document::finishParsing() [0x88c06e0] WebCore::DocumentWriter::endIfNotLoadingMainResource() [0x8aed3e1] WebCore::DocumentWriter::end() [0x8aed414] WebCore::DocumentLoader::finishedLoading() [0x8ae5eca] WebCore::FrameLoader::finishedLoading() [0x8afc7ee] WebCore::MainResourceLoader::didFinishLoading() [0x8b0b680] WebCore::ResourceLoader::didFinishLoading() [0x8b141af] WebCore::ResourceHandleInternal::didFinishLoading() [0x9318b8c] webkit_glue::WebURLLoaderImpl::Context::OnCompletedRequest() [0x8f425ba] (anonymous namespace)::RequestProxy::NotifyCompletedRequest() [0x8f6d675] DispatchToMethod<>() [0x8f6db0f] RunnableMethod<>::Run() [0x8f6db4a] MessageLoop::RunTask() [0x81522e5] MessageLoop::DeferOrRunPendingTask() [0x8152391] MessageLoop::DoWork() [0x8152621] base::MessagePumpForUI::RunWithDispatcher() [0x818f4f5] base::MessagePumpForUI::Run() [0x818fdf7] MessageLoop::RunInternal() [0x8152e53] MessageLoop::RunHandler() [0x8152e6d] MessageLoop::Run() [0x8152f11] TestShell::WaitTestFinished() [0x8052d15] TestShell::RunFileTest() [0x8053053] It looks like it started happening somewhere between r67898 and r67907. I suspect r67903, but I'm not positive. 282811 1 pnormand 2010-09-22 00:37:39 -0700 *** This bug has been marked as a duplicate of bug 46169 ***