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

Issue 690200 link

Starred by 1 user
Status: Fixed
Owner:
█ jcivelli@chromium.org
Last visit > 30 days ago
Closed: Feb 2017
Cc:
█ eisinger@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

V8 should not be initialized in the GPU process.

Project Member Reported by jcivelli@chromium.org, Feb 8 2017 
content_main_runner initialize V8 for all process types.
It should not be initialized in the GPU process.
Project Member

Comment 1 by bugdroid1@chromium.org, Feb 9 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/15ffa4689839fa575de38a25c89780450b83e9d0

commit 15ffa4689839fa575de38a25c89780450b83e9d0
Author: jcivelli <jcivelli@chromium.org>
Date: Thu Feb 09 18:01:30 2017

Don't initialize V8 in the GPU process.

Don't initialize V8 in the GPU process, V8 should not be used there.

BUG= 690200 

Review-Url: https://codereview.chromium.org/2687683006
Cr-Commit-Position: refs/heads/master@{#449348}

[modify] https://crrev.com/15ffa4689839fa575de38a25c89780450b83e9d0/content/app/content_main_runner.cc

Comment 2 by jcivelli@chromium.org, Feb 9 2017

Status: Fixed (was: Untriaged)
►

Sign in to add a comment