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

Issue 691724 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

PWAs don't open when network is down

Project Member Reported by sbirch@chromium.org, Feb 13 2017

Issue description

I was on WiFi this morning where I think all packets were being dropped. It looks like in that circumstance launching a PWA / WebAPK will freeze on a pre-splash screen instead of showing the PWA in offline mode (like you would get if you opened it in airplane mode.) I would guess we have something that depends on the network during startup which doesn't time out promptly while waiting for a response.

This may sound like a crazy edge case, but I think being resilient to dropped packets is likely important for bad cell connections where packet loss is common. We'll need to draw a line somewhere where it's better to just get the offline version.

Video (internal): https://drive.google.com/a/google.com/file/d/0B0CSHELto3lKNy1iOXMwOWkteVU/view?usp=sharing
 

Comment 1 by sbirch@chromium.org, Feb 13 2017

Cc: pkotw...@chromium.org
You know, using my phone some more today I wonder if this was a network issue. I'm also getting unresponsive PWAs on other screens (loaded content, splashscreen.)

+Peter, could this be related to the renderer issue you were investigating?
Yes, it could be related to the renderer issue that I am investigating. The renderer issue (caused by https://codereview.chromium.org/2675013002) snuck in last Monday. I guess that means that it affects Canary & Dev
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 14 2017

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

commit feb7ca146e6cd6662129d0b82dfe116b94d37ad1
Author: pkotwicz <pkotwicz@chromium.org>
Date: Tue Feb 14 02:37:20 2017

Fix WebAPK renderer not launching

WebApkSandboxedService creates ChildProcessServiceImpl via reflection.
https://codereview.chromium.org/2675013002 added a non public constructor to
ChildProcessServiceImpl causing construction-via-reflection to fail.

BUG= 691709 , 691724 

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

[modify] https://crrev.com/feb7ca146e6cd6662129d0b82dfe116b94d37ad1/content/public/android/java/src/org/chromium/content/app/ChildProcessServiceImpl.java

Status: Fixed (was: Available)
Tentatively marking this bug as fixed. Sam, please file a new bug if you see this issue again :)

Sign in to add a comment