Crash during audio recording on AIR |
|
Issue descriptionSteps: 1) Download and install kiosk app https://chrome.google.com/webstore/detail/airsecuretest/hblfbmjdaalalhifaajnnodlkiloengc 2) Choose Oregon as the state 3) Go to Practice Test 4) Set up with Grade 1 ELA 5) Go to test recording page. Try to record voice and playback I have not confirmed this issue yet personally. From AIR: Able to reproduce issue on OS stable v57.0.2987.137 Chrome OS: v57.0.2987.137 stable DEVICES: Samsung XE303 (Arm) Samsung XE550 (Intel) Samsung XE303* (Arm) Firmware Google_Snow.2695.132.0 Samsung XE303* (Arm)UserAgent: Mozilla/5.0 (X11; CrOS armv7| 9202.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.137 Safari/537.36 AIRSecureBrowser/2.8.0.0 Samsung XE550 (Intel) Firmware Google_Lumpy.2.111.0 Samsung XE550 (Intel) UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9202.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.137 Safari/537.36 AIRSecureBrowser/2.8.0.0 ENV:* PROD= https://oakspt.tds.airast.org/student Device: HP Xe11 (arm) User Agent : Mozilla/5.0 (X11;CrOS armv7l 9202.60.0) AppleWebKit/537.36 (KHTML,like Gecko) Chrome/57.0.2987.137 Safari/537.36 AIRSecureBrowser/2.8.0.0 Version: 57.0.2987.137 Platform: 9202.60.0 Stable Channel daisy_spring Firmware: Google_Spring.3824.129.0 Device: ACER c720p Touch User Agent : Mozilla/5.0 (X11;CrOS X86_64 9202.60.0) AppleWebKit/537.36 (KHTML,like Gecko) Chrome/57.0.2987.137 Safari/537.36 AIRSecureBrowser/2.8.0.0 Version: 57.0.2987.137 Platform: 9202.60.0 Stable Channel peppy Firmware: Google_Peppy.4389.93.0 Thanks, Raheel
,
Mar 30 2017
This sounds like the same problem I ran into back in M-55 (Issue 654833) but only happened on ARM devices. The problem disappeared at M-57 (build 9202.11.0) and I haven't seen it happen since then on my Mickey, Tiger or Fievel. I'll try the devices mentioned above using the specified build.
,
Mar 30 2017
Thanks. I just tested Peppy and could not repro.
,
Mar 31 2017
I tried a daisy_spring and was unable to cause a crash with five attempts of record/playback. In the old issue it would happen in one or two tries. |
|
►
Sign in to add a comment |
|
Comment 1 by maxkirsch@chromium.org
, Mar 30 2017