Bug 99147

Summary: [chromium] crash in fast/dom/shadow/shadowdom-for-progress-dynamic.html
Product: WebKit Reporter: jochen
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: dglazkov, morrita
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

jochen
Reported 2012-10-12 00:46:04 PDT
When running in the content_shell like this new-run-webkit-tests --chromium --debug --driver-name=content_shell --additional-drt-flag=--dump-render-tree --additional-drt-flag=--no-sandbox fast/dom/shadow/shadowdom-for-progress-dynamic.html I get the following crash: STDERR: base::debug::StackTrace::StackTrace() [0x51829e] STDERR: base::(anonymous namespace)::StackDumpSignalHandler() [0x5318c4] STDERR: 0x7f27e5ffdaf0 STDERR: WebCore::ElementAttributeData::isMutable() [0x1e8dc1a] STDERR: WebCore::Element::mutableAttributeData() [0x2772a16] STDERR: WebCore::StyledElement::ensureInlineStyle() [0x2771b1f] STDERR: WebCore::StyledElement::setInlineStyleProperty() [0x315afab] STDERR: WebCore::ProgressValueElement::setWidthPercentage() [0x2ea587e] STDERR: WebCore::HTMLProgressElement::didElementStateChange() [0x2de261d] STDERR: WebCore::HTMLProgressElement::parseAttribute() [0x2de2586] STDERR: WebCore::Element::attributeChanged() [0x30c6d99] STDERR: WebCore::StyledElement::attributeChanged() [0x315ac29] STDERR: WebCore::Element::didModifyAttribute() [0x30cce76] STDERR: WebCore::Element::setAttributeInternal() [0x30ce836] STDERR: WebCore::Element::setAttribute() [0x30c6cf8] STDERR: WebCore::ElementV8Internal::setAttributeCallback() [0x34bd1c8] STDERR: v8::internal::HandleApiCallHelper<>() [0x16a7a05] STDERR: v8::internal::Builtin_Impl_HandleApiCall() [0x16a75e3] STDERR: v8::internal::Builtin_HandleApiCall() [0x16a116c] STDERR: 0x5eab750618e Tracked in chromium here: http://code.google.com/p/chromium/issues/detail?id=155474
Attachments
Dimitri Glazkov (Google)
Comment 1 2012-10-12 08:54:36 PDT
It looks like the progress element's guts aren't being initialized properly.
Stephen Chenney
Comment 2 2013-04-09 17:07:20 PDT
Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.
Note You need to log in before you can comment on or make changes to this bug.