New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 798404 link

Starred by 1 user
Status: WontFix
Owner:
mlippautz@chromium.org
Closed: Jan 2018
Cc:
█ hpayer@chromium.org
palmer@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug

Blocked on:
issue 752185
issue 800348


Sign in to add a comment

v8::internal::V8::FatalProcessOutOfMemory on forms of ru.wargaming.net

Project Member Reported by kolos@chromium.org, Jan 2 2018 
Visiting and typing sign-in or sign-up pages on ru.wargaming.net causes a crash in Dev, Beta and Stable (M63).

https://ru.wargaming.net/shop/auth/oid/new/

http://redir.wargaming.net/d99v4ooe/?pub_id=cmenu_www.wgservice.net


#0 0x7f78480544dc base::debug::StackTrace::StackTrace()
#1 0x7f7848054041 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7f7848165330 <unknown>
#3 0x7f7839644102 v8::base::OS::Abort()
#4 0x7f7842ad0dd9 v8::internal::V8::FatalProcessOutOfMemory()
#5 0x7f7842eec0f2 v8::internal::Isolate::Init()
#6 0x7f7843105c95 v8::internal::Snapshot::Initialize()
#7 0x7f7842afef87 v8::IsolateNewImpl()
#8 0x7f78432cface gin::IsolateHolder::IsolateHolder()
#9 0x7f7840bf5cf9 
#
# Fatal process OOM in heap setup
#


Michael: please forward to correct persons.

Comment 1 by mlippautz@chromium.org, Jan 2 2018

Blockedon: 752185
Cc: palmer@chromium.org hpayer@chromium.org u...@chromium.org
Labels: OS-Linux
Status: WontFix (was: Untriaged)
palmer: fyi

The webpage spawns many (57) web workers, at least on initial load of https://ru.wargaming.net/shop/auth/oid/new/ with a fresh user profile.

Each of those workers requires ~512M reserved (but only few M committed) address space on 64bit which is a constraint of V8's JIT. This one may be gone or significantly smaller in future but still is required as of today.

On Linux, the sandbox limits how much virtual address space a renderer can actually reserve to ~8G for security reasons. V8 will thus fail to set up its heap after starting up a few workers. 

This issue has now surfaced in different variants (wasm reservations, webworkers, large google docs). I wonder if this should be addressed differently at some point.

Comment 2 by jgruber@chromium.org, Jan 9 2018

Blockedon: 800348
►

Sign in to add a comment