To reproduce: 1. run-javascriptcore-tests Three tests will hit an assertion. The tests are: js1_5/Regress/regress-152646.js js1_5/Regress/regress-192414.js js1_5/Regress/regress-96526-002.js The assertion is in Heap::destroy. It is: ASSERT(!m_globalData->dynamicGlobalObject); m_globalData->dynamicGlobalObject seems always to be 0x01500000. Here's the backtrace: > JavaScriptCore.dll!JSC::Heap::destroy() Line 90 + 0x28 bytes C++ jsc.exe!cleanupGlobalData(JSC::JSGlobalData * globalData=0x00f2be88) Line 364 C++ jsc.exe!main(int argc=6, char * * argv=0x00cfed00) Line 356 + 0x9 bytes C++ jsc.exe!__tmainCRTStartup() Line 597 + 0x17 bytes C kernel32.dll!_BaseProcessStart@4() + 0x23 bytes
Is there any way to skip JS tests?
<rdar://problem/8842022>
Looks like run-javascriptcore-tests has support for skipping tests.
I skipped these tests in r75392.
Maybe this was caused by r75289?
(In reply to comment #5) > Maybe this was caused by r75289? I would guess so, rather than disabling those tests, i think it would be better to rollout that patch.
Yes, please roll out the offending patch.
(...and re-enable the tests.)
I don't know what the offending patch is yet. I'm testing r75289 now.
Rolling out r75289 fixes the assertions.
:-(
Rolled out r75289 and r75392. I commented in bug 26276.