5 ms·
Hmm, it crashed the browser on me (iPad 3, safari). I went to the site, searched for a random band and picked a playlist (a large one ~500 songs if it helps).
by mbell 14y ago
Hmm, it crashed the browser on me (iPad 3, safari).
I went to the site, searched for a random band and picked a playlist (a large one ~500 songs if it helps). I went to the playlist view and started scrolling through the songs, relatively quickly. I noticed the "bar" at the bottom of the playlist view was flickering a lot, you could see the upcoming song rows through it when it flickered then 'bam' whole browser crashed. Relaunched safari, it still had the grooveshark tab open, almost instantly crashed again.
- cantankerous 14y agoTo be fair, is that a Safari problem or a Grooveshark problem?
- Steko 14y agoIf Grooveshark is advertising that it works on "all devices" then it's a Grooveshark problem.
- rich90usa 14y agoAs another commentator replied, it's something that we have to deal with. I can't speak for sure, but I think what we're running in to here is too many elements on the page. I'm sure I'm glossing over the finer details, but I'd expect whatever bugfix is made will address that.
- ftwinnovations 14y agoWorked great on my iPad. Suggestion: start on the Popular tab, not Search. There's already a dedicated search field, and when I got to the page the big empty search area made me think the page was broken. Starting on Popular also would give a one-click-to-experience factor. Very cool app!
- mmahemoff 14y agoUser doesn't know or care about whose fault it is. That makes it Grooveshark's problem to fix, since Apple won't anytime soon.
- rich90usa 14y agoThanks for the bug report! This particular problem is actually decently high in the bugtracker so I'd think we'd have something within the next few bugfix releases.