I'm not seeing this on ToT (M63).

I am seeing it on ToT M63. Maybe it's something specific to my device. Too bad we aren't in the same office, I could give you the repro.

dbbrooks: Please show the repro to billorr.

My theory is that we are hitting the 5-second timeout, but I'd like to see the repro to know for sure.

The assigned owner "offenwanger@chromium.org" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Can't get any repro that isn't the 5 second timeout issue. 5 second timeout issue occurs intermittently, seemingly related to memory availability (it's easy to make it happen if you have a few different apps open, it usually won't happen if it's just chrome). 

Note that this still happens every time for me. Chrome 63.0.3226.0

Very interesting, do you happen to throw some exception ?

So that we can tell user either:
- model is too heavy for you phone in VR
- you can try again after closing other apps and tabs

(otherwise it will be a guess game and it's not ideal...)

We don't have a special exception type for this particular issue, but it's not a bad idea.

Beyond that, though, I want to make sure the 5 second requirement is clear: We don't require that a new frame is produced every 5 seconds. We only require that ANY frame is produced within the _first_ 5 seconds after requestPresent resolves. The idea is simply that we don't want a page to kick into VR mode and only then kick off a multi-minute loading sequence during which nothing is displayed to the user.

Technically you could call requestPresent, immediately call requestAnimationFrame, clear the frame to a solid color, and submitFrame and this would satisfy the requirement. Please don't do that in an actual product, but it would help diagnose if this limit was your actual problem or not.

Ideally if you need to do some loading or aren't convinced your app can produce a frame within 5 seconds (which is a legitimate issue for user generated content) you should draw a single frame splash screen and just let the browser reproject it until you're ready to render more regularly.

And, of course, if you've already loaded all of the content for 2D rendering and are convinced that it's not going to take 5 seconds to render a frame you can just start the main render loop and move on.

Once you've satisfied the initial 5 second requirement we don't currently have any other similar limits, so if you hit the garbage-collect-from-hell and your app hangs for several seconds it won't boot you from VR.

Update - as of Chrome 64.0.3274.0 the issue has changed or disappeared. Now after hitting enter VR, I just see a 'This page isn't responding, you can wait for it or exit" message. See screenshot.

Deleted: Screenshot_20171122-053913.png 43.1 KB

	Screenshot_20171122-053913.png 43.1 KB View Download

This appear to not repro on current builds 66.0.3354.0 on Galaxy S6 device also verified on Pixel 2 using build 66.0.3355.0

We can close this issue as Fixed Externally.

Thanks.