889270 - The HTML 5 web app hosted at https://www.cubeslam.com/ does not load

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Siddharth]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20130701 Firefox/25.0 (Nightly/Aurora)
Build ID: 20130701031115

Steps to reproduce:

1.  Access https://www.cubeslam.com/


Actual results:

The screen shows Loading and does nothing further.


Expected results:

The screen should load and go to the game.

Comment 1

[Siddharth]

Just FYI, this is an issue in nightly build version 25.0a1 (2013-07-01)

Comment 2

[Loic]

There is probably a regression but it's hard to bisect due to crashes with this website (see bug 882589). :/

Comment 3

[Loic]

I think the regression range is:
good=2013-06-23
bad=2013-06-24
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4c4f75c20e9b&tochange=76820c6dff7b

Indeed, the crash occurs only when Firefox is able to load and display the game, so it shows indirectly a good build. If not, the loading page stays in infinite loop.

Web console:
[16:47:24.891] TypeError: (intermediate value).createGainNode is not a function @ https://www.cubeslam.com/javascript/slam.min.js?v=live.368036945984965839:7
[16:47:25.351] NS_ERROR_UNEXPECTED: Unexpected error @ https://www.cubeslam.com/javascript/slam.min.js?v=live.368036945984965839:4

Comment 4

[Alice0775 White]

(In reply to Loic from comment #3)
> I think the regression range is:
> good=2013-06-23
> bad=2013-06-24
> http://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=4c4f75c20e9b&tochange=76820c6dff7b
> 
> Indeed, the crash occurs only when Firefox is able to load and display the
> game, so it shows indirectly a good build. If not, the loading page stays in
> infinite loop.
> 
> Web console:
> [16:47:24.891] TypeError: (intermediate value).createGainNode is not a
> function @
> https://www.cubeslam.com/javascript/slam.min.js?v=live.368036945984965839:7
> [16:47:25.351] NS_ERROR_UNEXPECTED: Unexpected error @
> https://www.cubeslam.com/javascript/slam.min.js?v=live.368036945984965839:4

It crashes(bug 882589), if set media.webaudio.legacy.AudioContext = true.
So, I think this forever loading is caused by landing of Bug 886165.

Comment 5

[Loic]

Confirmed, yes.

Comment 6

[(no longer active)]

I'll try to find somebody inside Google who knows who to talk to about this.

Comment 7

[(no longer active)]

The demo was fixed yesterday to finish loading but there are still problems in it preventing audio playback from working.  The Google folks are working on a fix.

Comment 8

[bhavana bajaj [:bajaj]]

(In reply to :Ehsan Akhgari (needinfo? me!) from comment #7)
> The demo was fixed yesterday to finish loading but there are still problems
> in it preventing audio playback from working.  The Google folks are working
> on a fix.

Hey :Ehsan, is there any news about this yet ? Given Fx24 is going to be released soon, can we increase the sense of urgency from our side ?

Comment 9

[(no longer active)]

(In reply to comment #8)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #7)
> > The demo was fixed yesterday to finish loading but there are still problems
> > in it preventing audio playback from working.  The Google folks are working
> > on a fix.
> 
> Hey :Ehsan, is there any news about this yet ? Given Fx24 is going to be
> released soon, can we increase the sense of urgency from our side ?

Firefox 24 has Web Audio disabled, so should not be affected by this. Am I missing something?

Comment 10

[bhavana bajaj [:bajaj]]

(In reply to :Ehsan Akhgari (needinfo? me!) from comment #9)
> (In reply to comment #8)
> > (In reply to :Ehsan Akhgari (needinfo? me!) from comment #7)
> > > The demo was fixed yesterday to finish loading but there are still problems
> > > in it preventing audio playback from working.  The Google folks are working
> > > on a fix.
> > 
> > Hey :Ehsan, is there any news about this yet ? Given Fx24 is going to be
> > released soon, can we increase the sense of urgency from our side ?
> 
> Firefox 24 has Web Audio disabled, so should not be affected by this. Am I
> missing something?

Ah, my bad, sorry ! Marking the status flags appropriately to avoid confusion.

Comment 11

[(no longer active)]

I just contacted the CubeSlam team again.

Comment 12

[Alex Keybl [:akeybl]]

(In reply to :Ehsan Akhgari (needinfo? me!) from comment #11)
> I just contacted the CubeSlam team again.

Let me know if there's anything I can do to push this along as well.

Comment 13

[(no longer active)]

(In reply to Alex Keybl [:akeybl] from comment #12)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #11)
> > I just contacted the CubeSlam team again.
> 
> Let me know if there's anything I can do to push this along as well.

I have not yet heard back... :/

Comment 14

[Adam Stevenson [:adamopenweb]]

Issue still exists with audio.

Ehsan: I'm guessing we still haven't heard back?

Comment 15

[(no longer active)]

No :(

Comment 16

[Kohei Yoshino [:kohei]]

Added this bug to the site compat doc: https://developer.mozilla.org/en-US/Firefox/Releases/25/Site_Compatibility#Video.2FAudio

Comment 17

[Karl Dubost💡 :karlcow]

Cute bear. The site has been fixed.