deps: v8 - intermittent failure in mjsunit/regress/regress-crbug-514081

[mhdawson]

• Version: master
• Platform: x86
• Subsystem: deps/v8

Since the upgrade to V8 5.X we have seen this test fail 2/3 last runs.

https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark,v8test=v8test/62/console

=== mjsunit/regress/regress-crbug-514081 ===
Command: /home/iojs/workspace/node-test-commit-v8-linux/nodes/benchmark/v8test/v8test/deps/v8/out/x64.release/d8 --test --random-seed=2071122626 --stress-opt --always-opt --nohard-abort --nodead-code-elimination --nofold-constants /home/iojs/workspace/node-test-commit-v8-linux/nodes/benchmark/v8test/v8test/deps/v8/test/mjsunit/mjsunit.js /home/iojs/workspace/node-test-commit-v8-linux/nodes/benchmark/v8test/v8test/deps/v8/test/mjsunit/regress/regress-crbug-514081.js
exit code: -9
--- CRASHED ---

We did just pull in more fixes today so that might have some impact.

[bnoordhuis]

I suspect it's an out-of-memory error because the test tries to create a 2 GB ArrayBuffer. The -9 exit code a.k.a. SIGKILL is presumably the OOM killer at work. Is there an entry in the system log afterwards?

[mhdawson]

Not resolved by most recent updates to v8.

There does seem to be an entry in system log:

May  4 17:00:06 nodejsb1 kernel: [18186106.571835] d8 invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
May  4 17:00:06 nodejsb1 kernel: [18186106.571838] d8 cpuset=/ mems_allowed=0
May  4 17:00:06 nodejsb1 kernel: [18186106.571841] CPU: 4 PID: 16808 Comm: d8 Not tainted 3.13.0-65-generic #106-Ubuntu
May  4 17:00:06 nodejsb1 kernel: [18186106.571842] Hardware name: Supermicro X9SCI/X9SCA/X9SCI/X9SCA, BIOS 2.2 02/20/2015
May  4 17:00:06 nodejsb1 kernel: [18186106.571843]  0000000000000000 ffff88021f8d5a80 ffffffff81723f80 ffff880220a6c800
May  4 17:00:06 nodejsb1 kernel: [18186106.571845]  ffff88021f8d5b08 ffffffff8171e587 ffffffff81067a16 ffff88021f8d5ae0
May  4 17:00:06 nodejsb1 kernel: [18186106.571847]  ffffffff810c79dc 0000000000000011 ffff88022fff3e38 0000000000000000
May  4 17:00:06 nodejsb1 kernel: [18186106.571849] Call Trace:
May  4 17:00:06 nodejsb1 kernel: [18186106.571854]  [] dump_stack+0x45/0x56
May  4 17:00:06 nodejsb1 kernel: [18186106.571856]  [] dump_header+0x7f/0x1f1
May  4 17:00:06 nodejsb1 kernel: [18186106.571859]  [] ? put_online_cpus+0x56/0x80
May  4 17:00:06 nodejsb1 kernel: [18186106.571861]  [] ? rcu_oom_notify+0xcc/0xf0
May  4 17:00:06 nodejsb1 kernel: [18186106.571864]  [] oom_kill_process+0x1ce/0x330
May  4 17:00:06 nodejsb1 kernel: [18186106.571867]  [] ? security_capable_noaudit+0x15/0x20
May  4 17:00:06 nodejsb1 kernel: [18186106.571868]  [] out_of_memory+0x414/0x450
May  4 17:00:06 nodejsb1 kernel: [18186106.571870]  [] __alloc_pages_nodemask+0xa60/0xb80
May  4 17:00:06 nodejsb1 kernel: [18186106.571873]  [] alloc_pages_vma+0x9a/0x140
May  4 17:00:06 nodejsb1 kernel: [18186106.571876]  [] handle_mm_fault+0xb23/0xf10
May  4 17:00:06 nodejsb1 kernel: [18186106.571879]  [] __do_page_fault+0x184/0x570
May  4 17:00:06 nodejsb1 kernel: [18186106.571881]  [] ? do_mmap_pgoff+0x34e/0x3d0
May  4 17:00:06 nodejsb1 kernel: [18186106.571883]  [] ? set_next_entity+0x95/0xb0
May  4 17:00:06 nodejsb1 kernel: [18186106.571886]  [] ? __switch_to+0x16b/0x4d0
May  4 17:00:06 nodejsb1 kernel: [18186106.571888]  [] do_page_fault+0x1a/0x70
May  4 17:00:06 nodejsb1 kernel: [18186106.571890]  [] page_fault+0x28/0x30
May  4 17:00:06 nodejsb1 kernel: [18186106.571891] Mem-Info:
May  4 17:00:06 nodejsb1 kernel: [18186106.571892] Node 0 DMA per-cpu:

If we believe its simply the test trying to use too much memory I could just remove it from our runs.

[bnoordhuis]

I suppose that's the easiest option. I'm kind of surprised a 2 GB allocation is enough to trigger the OOM killer on a 64 bits host. How much physical memory does the machine have?

[mhdawson]

It has 8G, but the tests do run multiple variants of the same test so it may be when you get a number of them running at the same time.

[mhdawson]

Has also failed as:

=== mjsunit/regress/regress-crbug-514081 ===
Command: /home/iojs/workspace/node-test-commit-v8-linux/nodes/benchmark/v8test/v8test/deps/v8/out/x64.release/d8 --test --random-seed=-1558288947 --stress-opt --always-opt --nohard-abort --nodead-code-elimination --nofold-constants /home/iojs/workspace/node-test-commit-v8-linux/nodes/benchmark/v8test/v8test/deps/v8/test/mjsunit/mjsunit.js /home/iojs/workspace/node-test-commit-v8-linux/nodes/benchmark/v8test/v8test/deps/v8/test/mjsunit/regress/regress-crbug-514081.js
exit code: -9
--- CRASHED ---

[mhdawson]

PR opened: #6678