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

Issue 825312 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Proj-XR
Proj-XR-VR



Sign in to add a comment

Scrolling on "no content" crashes Chrome

Project Member Reported by cjgrant@chromium.org, Mar 23 2018

Issue description

This is a bit of a construed case, but it's completely reproducible.

- Outside VR, ensure that only one tab is open, an incognito tab.
- Enter VR, then use the overflow menu to close that one tab.
- You'll be brought to a black content quad, which itself isn't good, but not the subject of the bug here.
- Hover on the black content, and scroll.  You'll immediately crash the browser with:

signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
[FATAL:ui_input_manager.cc(199)] Check failed: gesture_list->front()->GetType() == blink::WebInputEvent::kGestureScrollEnd (15 vs. 12)

It is possible we should never get to this state, if we force the new tab page to spawn when all tabs are otherwise close.
 
FWIW I wasn't able to repro this when testing the no tab case.

I'm not sure how ui_input_manager.cc could even possibly be affected by the tab closing...
Labels: -M-68 M-69
In any case, let's investigate for M69, the fix in M68 is to make sure we always have a tab.
Is is possible that this bug was a dup of crbug.com/830121, for which a fix landed yesterday. Could you confirm mthiesse?
Status: Fixed (was: Available)
I mean, looks like it. Let's just close this and re-open if we get a repro.

Sign in to add a comment