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

Issue 663056 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome/Kiosk app crashes on ELPA recorder page

Reported by ad...@tdsstudentlogin.com, Nov 7 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14

Steps to reproduce the problem:
Steps to reproduce the problem:
1. Use the provided html test page.
2. Login with guest student
3. Start Grade 1 ELPA test
4. Reach to ELPA sound record page and try to record something
5. Now Play the Recorded Data

What is the expected behavior?
User should be able to record and play his recoded data and pass by the page without any issue.

What went wrong?
Notice the Kiosk will crash upon playing the recoded data is broken

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes 53, 54 on Touch system

Chrome version: 54.0.2840.87  Channel: stable
OS Version: 54.0.2840.87
Flash Version: 23.0.0.205-r1

Chrome version: 55.0.2883.35 Channel: Beta
Chrome Version: 56.0.2905.0 Channel: Dev
 
This is blocking support for us of Chrome version 53+ on non-touch device
I tested this and cannot repro in either the browser or the kiosk app, on 54 or 55. Are there additional instructions or requirements to repro?
Hi Max,

I had my QA retested this and this is now only getting reported in Asus C201P.

@Lyman or Max this is now effecting three models. AsusC201p, Samsung XE303 and HP XE11 G2+. Can you guys look into this
Guys, can you please provide some feedback on this, field is getting unhappy face when recorder starts. 
Components: OS>Kernel>Audio
Labels: M-54
Components: UI>Shell>Kiosk
I'm unable to repro on 55 or 56, but I don't have easy access to a device on 54.

Stable channel is currently 55, soon to be 56.  admin@tdsstudentlogin.com, can you test on 55?
Cc: harpreet@chromium.org mlight@chromium.org sduraisamy@chromium.org
Labels: Needs-Feedback
admin@tdsstudentlogin.com, did you get a chance to repro this on the latest ChromeOS Stable is, M55. 
Is this still  occurring?
I have seen a similar chrome renderer crash (the dead smiley-face) during record and playback of the AIRSecure Test app when using an ARM device (a "mickey" chromebit).  Issue 654833.
Per triage: admin@tdsstudentlogin.com please retest with 55. 
I just tested AIRSecure Test on M-57 Dev-channel build 9202.11.0.  I no longer get a renderer crash when doing record & playback.  Issue 654833 and  Issue 629328  don't have any indication of a fix being done, but it might be in some other ARM compiler or chip issue.
Status: WontFix (was: Unconfirmed)
admin@tdsstudentlogin.com, did you get a chance to repro this on the latest ChromeOS Stable is, M55. 
Is this still  occurring?

Closing this for now. Please do reopen/let us know if you see this occurring on the latest stable.

Sign in to add a comment