Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
mhdawson opened this issue Apr 21, 2016 · 6 comments
Closed
Labels
test Issues and PRs related to the tests. v8 engine Issues and PRs related to the V8 dependency.

Comments

@mhdawson
Copy link
Member

  • 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.

@mhdawson mhdawson added v8 engine Issues and PRs related to the V8 dependency. test Issues and PRs related to the tests. labels Apr 21, 2016
@bnoordhuis
Copy link
Member

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
Copy link
Member Author

mhdawson commented May 4, 2016

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
Copy link
Member

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
Copy link
Member Author

mhdawson commented May 9, 2016

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
Copy link
Member Author

mhdawson commented May 9, 2016

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
Copy link
Member Author

PR opened: #6678

evanlucas pushed a commit that referenced this issue May 17, 2016
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: #6340
PR-URL: #6678
Reviewed-By: Ben Noorhduis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
ofrobots pushed a commit to ofrobots/node that referenced this issue Aug 25, 2016
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noorhduis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
mhdawson added a commit to mhdawson/io.js that referenced this issue Oct 3, 2016
2d524bc

Original commit message:

deps: limit regress/regress-crbug-514081 v8 test

regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noorhduis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
mhdawson added a commit that referenced this issue Oct 5, 2016
2d524bc

Original commit message:

  deps: limit regress/regress-crbug-514081 v8 test

  regress/regress-crbug-514081 allocates a 2G block of memory
  and if there  are multiple variants running at the
  same time this can lead to crashes, OOM kills or
  the OS failing to allocate memory.  This patch
  limits us to running a single variant of the test

  Fixes: #6340
  PR-URL: #6678
  Reviewed-By: Ben Noordhuis <[email protected]>
  Reviewed-By: James M Snell <[email protected]>
  Reviewed-By: Fedor Indutny <[email protected]>

PR-URL: #8907
Fixes: #8750
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
jasnell pushed a commit that referenced this issue Oct 6, 2016
2d524bc

Original commit message:

  deps: limit regress/regress-crbug-514081 v8 test

  regress/regress-crbug-514081 allocates a 2G block of memory
  and if there  are multiple variants running at the
  same time this can lead to crashes, OOM kills or
  the OS failing to allocate memory.  This patch
  limits us to running a single variant of the test

  Fixes: #6340
  PR-URL: #6678
  Reviewed-By: Ben Noordhuis <[email protected]>
  Reviewed-By: James M Snell <[email protected]>
  Reviewed-By: Fedor Indutny <[email protected]>

PR-URL: #8907
Fixes: #8750
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
targos pushed a commit to targos/node that referenced this issue Dec 5, 2016
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noorhduis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
targos pushed a commit to targos/node that referenced this issue Dec 30, 2016
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noorhduis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Aug 31, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 1, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 2, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 3, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 4, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 5, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 6, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 6, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 7, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 8, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 9, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 10, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 11, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 12, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
targos pushed a commit to targos/node that referenced this issue Sep 12, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 13, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
addaleax pushed a commit that referenced this issue Sep 13, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: #6340
PR-URL: #6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
addaleax pushed a commit to addaleax/node that referenced this issue Sep 13, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
nodejs-ci pushed a commit to nodejs/node-v8 that referenced this issue Sep 14, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs/node#6340
PR-URL: nodejs/node#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
targos pushed a commit to targos/node that referenced this issue Sep 14, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
targos pushed a commit to targos/node that referenced this issue Sep 21, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: nodejs#6340
PR-URL: nodejs#6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
MylesBorins pushed a commit that referenced this issue Sep 28, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: #6340
Backport-PR-URL: #15393
PR-URL: #6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
MylesBorins pushed a commit that referenced this issue Sep 29, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: #6340
Backport-PR-URL: #15393
PR-URL: #6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
MylesBorins pushed a commit that referenced this issue Oct 3, 2017
regress/regress-crbug-514081 allocates a 2G block of memory
and if there  are multiple variants running at the
same time this can lead to crashes, OOM kills or
the OS failing to allocate memory.  This patch
limits us to running a single variant of the test

Fixes: #6340
Backport-PR-URL: #15393
PR-URL: #6678
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Issues and PRs related to the tests. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

No branches or pull requests

2 participants