Bug 128656
Summary: | REGRESSION: fast/workers/stress-js-execution.html crashes sometimes | ||
---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | fpizlo, ggaren, mhahnenberg, webkit-bug-importer |
Priority: | P1 | Keywords: | InRadar, Regression |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Alexey Proskuryakov
fast/workers/stress-js-execution.html started to flakily crash yesterday. Not frequently enough for me to pinpoint the revision.
http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=fast%2Fworkers%2Fstress-js-execution.html
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.JavaScriptCore 0x000000010831bd4a WTFCrash + 42 (Assertions.cpp:333)
1 com.apple.JavaScriptCore 0x0000000107c2126d JSC::SlotVisitor::unconditionallyAppend(JSC::JSCell*) + 77 (SlotVisitorInlines.h:123)
2 com.apple.JavaScriptCore 0x0000000107f7b2ad JSC::Heap::addToRememberedSet(JSC::JSCell const*) + 237 (Heap.cpp:788)
3 com.apple.JavaScriptCore 0x0000000107cdd638 JSC::CodeBlockSet::rememberCurrentlyExecutingCodeBlocks(JSC::Heap*) + 152 (CodeBlockSet.cpp:117)
4 com.apple.JavaScriptCore 0x0000000107f7b90e JSC::Heap::collect() + 1470 (Heap.cpp:929)
5 com.apple.JavaScriptCore 0x0000000107f6b294 JSC::DefaultGCActivityCallback::doWork() + 212 (GCActivityCallback.cpp:100)
6 com.apple.JavaScriptCore 0x0000000107f8c242 JSC::HeapTimer::timerDidFire(__CFRunLoopTimer*, void*) + 338 (HeapTimer.cpp:98)
7 com.apple.CoreFoundation 0x00007fff8e826724 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/16045354>
Mark Hahnenberg
Weird. A currently executing code block didn't mark its owner executable. That seems wrong.
Mark Hahnenberg
Same symptom as the bug 128745, so duping.
*** This bug has been marked as a duplicate of bug 128745 ***