The GTK JSC bot <https://build.webkit.org/#/builders/GTK-Linux-64-bit-Release-JS-Tests> has been failing for a long time, with crashes on all tests caused by two much memory usage.
basic-tests.yaml/stress-test.js.no-ftl: Running mandatory iteration #1:
basic-tests.yaml/stress-test.js.no-ftl: Crashing because current footprint: 633380864 exceeds limit: 629145600
basic-tests.yaml/stress-test.js.no-ftl: 1 0x55762feeb519 WTFCrash
basic-tests.yaml/stress-test.js.no-ftl: 5 0x7fb909d4b4d2 /usr/lib/x86_64-linux-gnu/libpthread.so.0(+0x84d2) [0x7fb909d4b4d2]
basic-tests.yaml/stress-test.js.no-ftl: 6 0x7fb908086323 clone
basic-tests.yaml/stress-test.js.no-ftl: ERROR: Unexpected exit code: 139
I have bisected this and the cause is r274166, also I have double-checked that by reverting locally this commit the issue is fixed.
The problem can be easily reproduced with this command:
Then almost all the JSC tests starts crashing due to trying to use more than the memory limit (which is 600 MB when passing --memory-limit) with a log like the above one.
- If you don't pass --memory-limit then your machine may crash due to OOM
- Passing --no-testb3 and --no-testapi is needed to avoid also an OOM crash because the testb3 and testapi tests don't seem to honour the --memory-limit switch
The issue is not happening on WPE, only on GTK
Bug 222972 seems related
Let's revert then.
Unfortunately there's no way I can debug something like this. It would need to be investigated by the JSC developers.
Created attachment 435999 [details]
Committed r281333 (240750@main): <https://commits.webkit.org/240750@main>