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

Issue 831077 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Blink not reporting correct V8 Isolate foreground/background status for startup scenario

Project Member Reported by mlippautz@chromium.org, Apr 10 2018

Issue description

Blink does not properly report foreground status when Chrome is started up freshly with a single tab.

Foreground tab status is not properly propagated when Chrome is run with a single tab. 

What steps will reproduce the problem?
(1) Add prints to v8::Isolate::IsolateInForegroundNotification and v8::Isolate::IsolateInBackgroundNotification
(2) out/Release/chrome --user-data-dir=/tmp/newuser 

Tested:
- When starting with a specific page
- When navigating away from the newtab page (clicking on a thumbnail)
- When navigating away using the omnibar

What is the expected result?
  Tab running with foreground notification.

What happens instead?
  IsolateInBackgroundNotification fires and puts the isolate in "background mode".

"Sometimes" we get the foreground notification when starting up without a specific page set and the user already exists.
 
Cc: mlippautz@chromium.org
Owner: ----
Status: Available (was: Assigned)
Status: WontFix (was: Available)
This is working as intended.
Using PrintIsolate unveils that the background notification is for a different renderer.

Sign in to add a comment