Flash hangs Grooveshark but is never killed, no effect on browser performance




9 years ago
2 years ago


(Reporter: ashughes, Unassigned)


1.9.2 Branch

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [Fx3.6.3plugin2])



9 years ago
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20100329 Lorentz/3.6.3plugin2pre

FLASH: Shockwave Flash 10.1 d51 (x64 build from Labs)

When listening to music on listen.grooveshark.com, the song suddenly stopped playing halfway through.  I was not able to restart playback of the song or start playback of another song.  When I attempted to reload the webpage, the LOADING page appeared but nothing was loading.  Flash appears to have locked up completely.

However, there is no performance hit to Firefox or my system.  I can also play flash videos in other tabs, so Flash is still working in other instances.  It is just the Grooveshark instance which is stalled.

I have the following tabs open in order of left-to-right:
Facebook > Grooveshark > Blues News > Engadget > Digg > Arstechnica > Vimeo

1. Open the tabs above
2. Play a video on Vimeo
3. Go to Grooveshark and start playing a song
4. Browse the web for a while

Song stops playing part way through (almost 50% of the way through in my case).
Reload the page and see the loading screen lock

If Flash is hung, kill it and allow me to restart Grooveshark.

Comment 1

9 years ago
A couple other things to note...

I have about 35 songs in my play queue which are restored from session:
1. Add 35 songs to your queue
2. Close the tab with Grooveshark loaded
3. Open a new tab and navigate to listen.grooveshark.com
4. Grooveshark asks if you want to restore your previous queue
5. Opt to restore
6. Start playing the first song in the queue

Another thing to note is that I have to restart my browser to get Grooveshark working again.

I cannot reproduce this behaviour on Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a4pre) Gecko/20100329 Minefield/3.7a4pre


9 years ago
Whiteboard: [Fx3.6.3plugin2]

Comment 2

9 years ago
This is not always reproducible. In other words, it will not happen every time on the first song and will not happen on every song.  Is there some kind of "texty" output I can generate next time I see this happen?

Comment 3

9 years ago
mozilla-central also, or just Lorentz?

Comment 4

9 years ago
I've been unable to reproduce this on moz-central.

Comment 5

9 years ago
I've been trying to reproduce this on Lorentz now for a couple of hours and have not noticed the issue appear again.  I'll keep testing this over the next while but due to it's low reproducibility, I would not hold the release for this.

Comment 6

9 years ago
Ok, it happened again on Lorentz.  This time causing RAM and CPU usage to spike to 100%.  It actually caused Pidgin to kill itself due to out of memory issues.  Grooveshark again stopped playing.  This time when I reloaded the page, however, it loaded but could not play any of the songs in my queue.  I had to restart Lorentz to fix it.

Comment 7

9 years ago
I would say this is most likely related to the other "Flash Hang" bug (bug number?).  The behaviour I am seeing is most likely specific to how Grooveshark is reacting to it.  So I'm not sure if this is a new issue, related to, or should just be duped against that bug.

Comment 8

2 years ago
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.