Bug 155526 - REGRESSION: JSC test stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool failing
Summary: REGRESSION: JSC test stress/materialize-past-butterfly-allocation.js.ftl-no-c...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Macintosh Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-15 18:22 PDT by Ryan Haddad
Modified: 2016-04-08 14:15 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2016-03-15 18:22:41 PDT
JSC stress test failure: stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool

Encountered this failure on El Capitan and Yosemite Debug JSC tests.

<https://build.webkit.org/builders/Apple%20Yosemite%20Debug%20JSC%20%28Tests%29/builds/5295>
<https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20JSC%20%28Tests%29/builds/2125>

stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: Timed out after 339.000000 seconds!
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 1   0x10afd8a40 WTFCrash
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 2   0x109ede0aa timeoutThreadMain(void*)
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 3   0x10b043c39 WTF::createThread(void (*)(void*), void*, char const*)::$_0::operator()() const
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 4   0x10b043c0d void std::__1::__invoke_void_return_wrapper<void>::__call<WTF::createThread(void (*)(void*), void*, char const*)::$_0&>(WTF::createThread(void (*)(void*), void*, char const*)::$_0&&&)
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 5   0x10b043bac std::__1::__function::__func<WTF::createThread(void (*)(void*), void*, char const*)::$_0, std::__1::allocator<WTF::createThread(void (*)(void*), void*, char const*)::$_0>, void ()>::operator()()
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 6   0x10a8e1eda std::__1::function<void ()>::operator()() const
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 7   0x10b04290e WTF::threadEntryPoint(void*)
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 8   0x10b0441a1 WTF::wtfThreadEntryPoint(void*)
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 9   0x7fff9aefac13 _pthread_body
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 10  0x7fff9aefab90 _pthread_body
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: 11  0x7fff9aef8375 thread_start
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: test_script_15145: line 2: 39785 Segmentation fault: 11  ( "$@" ../../.vm/JavaScriptCore.framework/Resources/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --jitMemoryReservationSize\=50000 --useFTLJIT\=true --useConcurrentJIT\=false --thresholdForJITAfterWarmUp\=100 materialize-past-butterfly-allocation.js )
stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool: ERROR: Unexpected exit code: 139
FAIL: stress/materialize-past-butterfly-allocation.js.ftl-no-cjit-small-pool
Comment 1 Ryan Haddad 2016-03-15 18:25:43 PDT
Last passing run was r198211, this test has been failing since then.
Comment 2 Filip Pizlo 2016-03-15 18:30:26 PDT
I think that this is just a super inefficient test.  I don't think it tests anything super important.  I'm OK with simply deleting this test.
Comment 3 Ryan Haddad 2016-03-17 10:44:53 PDT
(In reply to comment #2)
> I think that this is just a super inefficient test.  I don't think it tests
> anything super important.  I'm OK with simply deleting this test.

Will you be able to take care of this?
Comment 4 Alexey Proskuryakov 2016-03-23 10:46:53 PDT
Interestingly, this test now fails every time on debug: <https://build.webkit.org/builders/Apple%20Yosemite%20Debug%20JSC%20(Tests)?numbuilds=50>.

Something must be getting progressively slower.

FWIW, the test was added in http://trac.webkit.org/changeset/181817
Comment 5 Alexey Proskuryakov 2016-04-08 14:15:06 PDT
Did this stop happening on its own?