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

Issue 920662 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Cc:
█ kbr@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Javascript in Kiosk App crashes - no way to now use API to report crash and restart

Reported by jseli...@intouchlink.net, Jan 10 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Platform: 11021.81.0 (Official Build) stable-channel veyron-fievel

Steps to reproduce the problem:
1. We use chromebox devices that are Enterprise managed through the Google Device Management console
2. We have a custom kiosk app that runs a signage player in the Chrome browser
3. The Javascript crashes in some cases after the signage has been running for 24 hours or so
4. Any App API calls (from here: https://developer.chrome.com/apps/api_index) run in Javascript, so we can't monitor the channel actually running and restart accordingly

What is the expected behavior?
We should be able to run the APIs even if Javascript has crashed. 

OR Javascript should auto-restart if it crashes.

What went wrong?
Chrome crashes (see attached log), but it seems the Javascript also crashes and we can't use any of the APIs.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.110  Channel: stable
OS Version: 70.0.3538.110
Flash Version: 31.0.0.148
logs_20190110-0938.zip
894 KB Download

Comment 1 by hablich@chromium.org, Today (21 hours ago)

Cc: mlippautz@chromium.org
Can you please provide a crashID?
What do you mean with "JavaScript crashes"?

This sounds like the app is allocating memory continuously and runs out of memory after some time.

Comment 2 Deleted

Comment 3 by jseli...@intouchlink.net, Today (13 hours ago) 

Attached is a log of a device that experienced the crash at around 1:59 on January 6, 2019.

Perhaps you can find something in the logs. We have a number of logs with corresponding crash times but we haven't been able to find a consistent issue across the multiple crash times.
logs_20190106-2251 (1).zip
1.1 MB Download

Comment 4 by jseli...@intouchlink.net, Today (13 hours ago) 

Crash ID in the above are: 62813fb07081a259 and c36bdc7930cad214

Comment 5 by jseli...@intouchlink.net, Today (13 hours ago) 

Here's a video of what the test channel looks like frozen. As you can see the screen has frozen, but the audio continues to rotate in the background (the beeping signifies the end of the test countdown video).
20190107_112403.mp4
12.9 MB View Download

Comment 6 by mlippautz@chromium.org, Today (13 hours ago)

Cc: -mlippautz@chromium.org kbr@chromium.org
Components: -Blink>JavaScript Internals>GPU>Internals
62813fb07081a259 does not contain a stack trace.

c36bdc7930cad214 is around GPU.

Re-triaging appropriately.
►

Sign in to add a comment