[Webkit-unassigned] [Bug 215447] New: stress/collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js is flaky on aarch64

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=215447

            Bug ID: 215447
           Summary: stress/collect-continuously-should-not-wake-concurrent
                    -collector-after-prevent-collection-is-called.js is
                    flaky on aarch64
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at gnome.org

Our internal CI has detected stress/collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js crashing twice now: first on Wednesday last week, then again this morning. I've never seen this test crashing before, so I think a recent change is trunk is likely the culprit:

Running stress/collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js.default
stress/collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js.default: test_script_5107: line 2: 1377376 Segmentation fault      (core dumped) ( "$@" /home/jenkins/workspace/WebKit-JSC/label/aarch64/WebKitBuild/Release/bin/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --validateExceptionChecks\=true --useDollarVM\=true --maxPerThreadStackUsage\=1572864 --useFTLJIT\=true --maxPerThreadStackUsage\=1572864 --forceMiniVMMode\=1 --stealEmptyBlocksFromOtherAllocators\=0 --collectContinuously\=1 --watchdog\=3000 --watchdog-exception-ok collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js )
stress/collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js.default: ERROR: Unexpected exit code: 139
FAIL: stress/collect-continuously-should-not-wake-concurrent-collector-after-prevent-collection-is-called.js.default

Since we can't get a backtrace from the CI, it is effectively impossible to fix unless somebody can reproduce it, but I'm reporting this anyway just in case somebody manages to reproduce it in the future.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200813/d4432488/attachment-0001.htm>