Bug 82374 – media/track/track-delete-during-setup.html is crashing on debug chromium bots

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Tools / Tests

[Dirk Pranke]

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=media%2Ftrack%2Ftrack-delete-during-setup.html

e.g.:

crash log for DumpRenderTree (pid 59250):
STDOUT: <empty>
STDERR: SHOULD NEVER BE REACHED
STDERR: third_party/WebKit/Source/WebCore/html/track/LoadableTextTrack.cpp(147) : size_t WebCore::LoadableTextTrack::trackElementIndex()
STDERR: 1   0x1055971
STDERR: 2   0x105ad60
STDERR: 3   0xf9093a
STDERR: 4   0xfc0f1e
STDERR: 5   0x6b5475
STDERR: 6   0x6b38fe
STDERR: 7   0x73efcc
STDERR: 8   0x132b229
STDERR: 9   0xb2bcdd
STDERR: 10  0xb26774
STDERR: 11  0xb26745
STDERR: 12  0x2394a280618e
STDERR: [59250:59250:18391688772239:ERROR:process_util_posix.cc(142)] Received signal 11
STDERR: 	base::debug::StackTrace::StackTrace() [0x857dea]
STDERR: 	base::(anonymous namespace)::StackDumpSignalHandler() [0x8119cd]
STDERR: 	0x7f1c92354af0
STDERR: 	WebCore::LoadableTextTrack::trackElementIndex() [0x105597b]
STDERR: 	WebCore::TextTrackList::append() [0x105ad60]
STDERR: 	WebCore::HTMLMediaElement::didAddTrack() [0xf9093a]
STDERR: 	WebCore::HTMLTrackElement::insertedIntoTree() [0xfc0f1e]
STDERR: 	WebCore::notifyChildInserted() [0x6b5475]
STDERR: 	WebCore::ContainerNode::appendChild() [0x6b38fe]
STDERR: 	WebCore::Node::appendChild() [0x73efcc]
STDERR: 	WebCore::V8Node::appendChildCallback() [0x132b229]
STDERR: 	v8::internal::HandleApiCallHelper<>() [0xb2bcdd]
STDERR: 	v8::internal::Builtin_Impl_HandleApiCall() [0xb26774]
STDERR: 	v8::internal::Builtin_HandleApiCall() [0xb26745]
STDERR: 	0x2394a280618e

Eric, Emil tells me you might've been working in this area and seen this crash before? he mentioned you had track-related changes in r111581 and 111941 ?

[Eric Carlson]

Adam wrote this up yesterday as https://bugs.webkit.org/show_bug.cgi?id=82269, I just haven't had a spare minute to look into it yet.

*** This bug has been marked as a duplicate of bug 82269 ***