Bug 187483 – JSC Debug stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory

• Component: Tools / Tests
• Status: NEW

[Dawei Fenton (:realdawei)]

JSC Debug stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit

This error is showing up frequently on JSC Debug High Sierra:
https://build.webkit.org/builders/Apple%20High%20Sierra%20Debug%20JSC%20%28Tests%29/builds/1244/steps/jscore-test/logs/stdio

stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: Timed out after 508.500000 sec seconds!
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 1   0x10fadba59 WTFCrash
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 2   0x10f89ac66 startTimeoutThreadIfNeeded()::$_7::operator()() const
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 3   0x10f89ab99 WTF::Function<void ()>::CallableWrapper<startTimeoutThreadIfNeeded()::$_7>::call()
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 4   0x10fb00c2b WTF::Function<void ()>::operator()() const
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 5   0x10fb84e7f WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*)
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 6   0x10fb8a825 WTF::wtfThreadEntryPoint(void*)
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 7   0x7fff6eb48661 _pthread_body
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 8   0x7fff6eb4850d _pthread_body
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 9   0x7fff6eb47bf9 thread_start
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: test_script_25905: line 2: 81214 Segmentation fault: 11  ( "$@" ../../.vm/JavaScriptCore.framework/Resources/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --validateExceptionChecks\=true --useDollarVM\=true --maxPerThreadStackUsage\=1572864 --useFTLJIT\=true --useConcurrentJIT\=false --thresholdForJITAfterWarmUp\=100 --scribbleFreeCells\=true --timeoutMultiplier\=1.5 string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js )
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: ERROR: Unexpected exit code: 139
FAIL: stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit

[Dawei Fenton (:realdawei)]

It looks like this was also an issue in the Yosemite era:
https://bugs.webkit.org/show_bug.cgi?id=164630

and the resolution was to give the test more time to run:
https://trac.webkit.org/changeset/209724/webkit

[Dawei Fenton (:realdawei)]

This test time out again today.

Possible resolution would be to tweak "--timeoutMultiplier"

https://build.webkit.org/builders/Apple%20High%20Sierra%20Debug%20JSC%20%28Tests%29/builds/1272/steps/jscore-test/logs/stdio
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: Timed out after 508.500000 sec seconds!
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 1   0x107bc7e49 WTFCrash
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 2   0x104115b26 startTimeoutThreadIfNeeded()::$_7::operator()() const
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 3   0x104115a59 WTF::Function<void ()>::CallableWrapper<startTimeoutThreadIfNeeded()::$_7>::call()
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 4   0x107bed01b WTF::Function<void ()>::operator()() const
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 5   0x107c7146f WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*)
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 6   0x107c76e15 WTF::wtfThreadEntryPoint(void*)
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 7   0x7fff6eb48661 _pthread_body
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 8   0x7fff6eb4850d _pthread_body
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: 9   0x7fff6eb47bf9 thread_start
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: test_script_25979: line 2: 38080 Segmentation fault: 11  ( "$@" ../../.vm/JavaScriptCore.framework/Resources/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --validateExceptionChecks\=true --useDollarVM\=true --maxPerThreadStackUsage\=1572864 --useFTLJIT\=true --useConcurrentJIT\=false --thresholdForJITAfterWarmUp\=100 --scribbleFreeCells\=true --timeoutMultiplier\=1.5 string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js )
stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit: ERROR: Unexpected exit code: 139
FAIL: stress/string-prototype-replace-should-throw-out-of-memory-error-when-using-too-much-memory.js.misc-ftl-no-cjit

[Dawei Fenton (:realdawei)]

Seeing this timeout much more frequently.  It has timed-out for 5 consecutive runs.

https://build.webkit.org/builders/Apple%20High%20Sierra%20Debug%20JSC%20(Tests)?numbuilds=50

[Mark Lam]

Does it only time out on debug builds?  Does it ever timeout on release builds?

[Dawei Fenton (:realdawei)]

(In reply to Mark Lam from comment #4)
> Does it only time out on debug builds?  Does it ever timeout on release
> builds?

so far I've only seen it time out on Debug builds.