ICY streams not unloaded correctly

RESOLVED INACTIVE

Status

()

RESOLVED INACTIVE
5 years ago
3 months ago

People

(Reporter: nick, Unassigned)

Tracking

24 Branch
ARM
Gonk (Firefox OS)
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Testing on a Unagi with a 1.2 build from August 1st.

STR:
1. Open browser app
2. Navigate to `50.117.121.10/;`, do not forget the `/;`
3. ShoutCAST mp3 stream over ICY protocol should play (this stream could theoretically go down in the future, it's not mine)
4. Open new tab and close the ShoutCAST tab (or restart the browser app)
5. In new tab, browse back to `50.117.121.10/;`

Expected:
ShoutCAST stream should play again

Actual:
Stream will not play again until device is restarted


I don't know anything about the media layers, but I recall hearing that mp3 files that were being decoded in hardware (on device) needed to be manually unloaded. Ex.

audio.src = null;
audio.load();

I'm not sure that that is the issue, but if it is, then this bug should probably be moved to the gaia browser component.
Also, I have not tested it, but this could be the case for mp3s in general in the browser app (when they are loaded as the only resource in the URI, not via the source attribute of an audio element).

Comment 2

5 years ago
Are you able to try STR on a non-ICY stream? I have an mp3 at http://cd.pn/a but don't have a gonk device handy to try.
@doublec, I just tested your mp3 on 1.2 and 1.0.1 and it worked, no problems.  So that rules out gaia::browser issues.
blocking-b2g: --- → koi?

Comment 4

5 years ago
Nick, could you give us more information about why this is nominated to 1.2
Flags: needinfo?(nick)
After further testing this isn't a huge issue.  When using an Audio element, there are no problems.  It only seems to affect Gaia browser when navigating directly to a stream.  ICY support is important for third party internet radio app developers.
Flags: needinfo?(nick)
(In reply to Nick Desaulniers [:\n] from comment #5)
> After further testing this isn't a huge issue.  When using an Audio element,
> there are no problems.  It only seems to affect Gaia browser when navigating
> directly to a stream.  ICY support is important for third party internet
> radio app developers.

I'll followup over email on this. I need more details if this is blocking a target 1.2 partner or not.
Talked with Nick offline - this isn't a blocker for 1.2, only cause it impacts use cases when browsing directly to a stream.
blocking-b2g: koi? → ---
Component: Audio/Video → Audio/Video: Playback

Comment 8

3 months ago
Mass closing do to inactivity.
Feel free to re-open if still needed.
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.