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

Issue 678509 link

Starred by 2 users
Status: WontFix
Owner:
rtoy@chromium.org
Closed: Feb 2017
Cc:
nyerramilli@chromium.org
kkaluri@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Treasure Arena app doesn't load after clicking on it from chrome://apps/

Reported by vku...@etouch.net, Jan 5 2017 
Chrome Version: 57.0.2971.0 32fb89992da01de660b893d746916f587e871dc9-refs/heads/master@{#441288} (64-bit)
OS:Windows(7,8,8.1,10)

What steps will reproduce the problem?
(1)Launch chrome and install "Treasure arena" from https://chrome.google.com/webstore/detail/treasure-arena/hedpcboianohjgdhoblpcpgapknkoojm?hl=en-GB
(2)After loading the app click on it and observe.

Actual: Treasure Arena app doesn't load after clicking on it.

Expected:  Treasure Arena app should load after clicking on it.

This is a regression issue broken in 'M57' and below is the manual regression range:
Good Build: 57.0.2952.0
Bad Build:  57.0.2953.0

Note: Issue not seen on Mac & Linux OS.
Actual_App.mp4
182 KB View Download
Expected_App.mp4
303 KB View Download

Comment 1 by brajkumar@chromium.org, Jan 5 2017

Labels: hasbisect-per-revision ReleaseBlock-Stable
Owner: rtoy@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,

You are probably looking for a change made after 438986 (known good), but no later than 438987 (first known bad).

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/5e87e713d6ed8c36fb37b814c6b65e7096d4554e..f58de349230213827cd1e057d10b7a61411c328a

From the CL above, assigning the issue to the concern owner
Review-Url: https://codereview.chromium.org/2557523002

rtoy@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Note: Adding RB-Stable since this is a recent regression, please feel free to edit if this is not the case.

Thanks!

Comment 2 by hongchan@chromium.org, Jan 5 2017 

It seems like the app code contains 'webkitAudioContext', we did not see any error message from it. The attachment is the console message from the game when it's stuck at 76% of "loading audio" phase.
Screen Shot 2017-01-05 at 09.54.37.png
69.0 KB View Download

Comment 3 by rtoy@chromium.org, Jan 5 2017

Labels: Needs-Feedback
Examining the code indicates that if new webkitAudioContext() fails, it falls back to sm2 (SoundManager?).  So in Chrome 57, it's using SoundManager instead of WebAudio; so perhaps the bug is there.

In any case, the app should test for both webkitAudioContext() and AudioContext()

Comment 4 by ajha@chromium.org, Jan 13 2017 

Friendly ping to get an update on this.

Comment 5 by rtoy@chromium.org, Jan 17 2017 

Another ping for additional info.  AFAICT, Chrome is doing the right thing because the prefixed WebAudio AudioContext has been removed as planned.

Comment 6 by ajha@chromium.org, Jan 23 2017

Components: Blink>WebAudio
Labelling the bug accordingly to get an update from Devs as per C#5.

Comment 7 by kkaluri@chromium.org, Jan 30 2017

Cc: kkaluri@chromium.org
Tested this issue in windows 10 with chrome canary version #58.0.2997.0, observed that the "Treasure Arena" app is loading successfully.

Attaching the screen-cast for your reference, vkupte@ could you please look into it and let us know your observations
Issue 678509.mp4
2.1 MB View Download

Comment 8 by brajkumar@chromium.org, Feb 7 2017 

vkupte@ could you please respond for the comment #7 by rechecking this issue on chrome latest canary #58.0.3004.1.

Thanks!

Comment 9 by vku...@etouch.net, Feb 7 2017

Labels: -Needs-Feedback
With response to comment #7 & #8:
Rechecked above issue on latest canary version 58.0.3004.1 and observed that the "Treasure Arena" app is loading properly.

Comment 10 by gov...@chromium.org, Feb 8 2017 

A friendly reminder that M57 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

Comment 11 by rtoy@chromium.org, Feb 8 2017

Status: WontFix (was: Assigned)
Wontfix: WAI.
►

Sign in to add a comment