Bug 131919 – REGRESSION (r167530): ASSERT(m_selfTime <= m_totalTime) on tests that run after certain Inspector tests

• Status: RESOLVED
• Resolution: FIXED
• Component: JavaScriptCore

[Alexey Proskuryakov]

js/dom/JSON-stringify.html started to ASSERT very frequently after <http://trac.webkit.org/r167530>:

0   com.apple.JavaScriptCore      	0x000000010abc44ea WTFCrash + 42 (Assertions.cpp:333)
1   com.apple.JavaScriptCore      	0x000000010aadb068 JSC::ProfileNode::stopProfiling() + 360 (ProfileNode.cpp:133)
2   com.apple.JavaScriptCore      	0x000000010aad46d8 JSC::Profile::forEach(void (JSC::ProfileNode::*)()) + 328 (Profile.cpp:65)
3   com.apple.JavaScriptCore      	0x000000010aad958a JSC::ProfileGenerator::stopProfiling() + 74 (ProfileGenerator.cpp:162)
4   com.apple.JavaScriptCore      	0x000000010a993c5d JSC::LegacyProfiler::stopProfiling(JSC::JSGlobalObject*) + 109 (LegacyProfiler.cpp:112)
5   com.apple.JavaScriptCore      	0x000000010a8d70f9 JSC::JSGlobalObject::~JSGlobalObject() + 121 (JSGlobalObject.cpp:188)
6   com.apple.WebCore             	0x000000010d4513b5 WebCore::JSDOMGlobalObject::~JSDOMGlobalObject() + 85 (JSDOMGlobalObject.h:43)
7   com.apple.WebCore             	0x000000010d4e7c11 WebCore::JSDOMWindowBase::~JSDOMWindowBase() + 49 (JSDOMWindowBase.h:37)
8   com.apple.WebCore             	0x000000010d4e4615 WebCore::JSDOMWindowBase::~JSDOMWindowBase() + 21 (JSDOMWindowBase.h:37)
9   com.apple.WebCore             	0x000000010d4e3885 WebCore::JSDOMWindowBase::destroy(JSC::JSCell*) + 21 (JSDOMWindowBase.cpp:84)
10  com.apple.JavaScriptCore      	0x000000010a7df626 JSC::Heap::FinalizerOwner::finalize(JSC::Handle<JSC::Unknown>, void*) + 70 (Heap.cpp:1309)
11  com.apple.JavaScriptCore      	0x000000010ab7f1ed JSC::WeakBlock::finalize(JSC::WeakImpl*) + 189 (WeakSetInlines.h:52)
12  com.apple.JavaScriptCore      	0x000000010ab7eb6e JSC::WeakBlock::sweep() + 158 (WeakBlock.cpp:77)

[Alexey Proskuryakov]

Worst of all, it's likely some preceding test that's breaking things.

How important was r167530? It broke at least two tests in mysterious ways, can we just not do this at this time?

[Alexey Proskuryakov]

I can reproduce with:

run-webkit-tests --child-processes=1 inspector/dom/content-flow-list.html js/dom/JSON-parse.html --v --repeat-each 10

So, it's inspector/dom/content-flow-list.html that causes this assertion failure.

[Timothy Hatcher]

That change is important. I'll look into the crashes / failures. Unlike the GC failure, this one is actually related to my change.

[Alexey Proskuryakov]

There are many tests that randomly assert because of this - at least half a dozen of js/dom tests do, apparently depending on how quickly garbage collection occurs. So, it would not make a lot of sense to mark these as flakily crashing.

Skipped all inspector/dom tests in <http://trac.webkit.org/r167593>, in hopes that these are the only ones that cause trouble. Also commented out flakiness expectations that we had for some of these.

[Timothy Hatcher]

<rdar://problem/16713655>

[Timothy Hatcher]

I suspect https://trac.webkit.org/changeset/167647 might have fixed this.

[Joseph Pecoraro]

I don't see these anymore, closing this bug.