Closed
Bug 1102155
Opened 11 years ago
Closed 11 years ago
[Flame][Browser]Can't reopen youtube after lost network and connect agian.
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 unaffected, b2g-master unaffected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| b2g-v2.0 | --- | affected |
| b2g-v2.1 | --- | affected |
| b2g-v2.2 | --- | unaffected |
| b2g-master | --- | unaffected |
People
(Reporter: huayu.li, Unassigned)
Details
(Whiteboard: [systemsfe])
Attachments
(3 files)
[1.Description]:
[Flame][2.1][Browser]If we lost network while playing video on youtube.com,we can't continue playing after network recovered.
Occurence time:15:53
see attachments:logcat.txt,video 1.3gp.
[2.Testing Steps]:
1.Launch browser.
2.Input www.youtube.com.
3.Tap a video to play.
4.Lost network (wifi) while playing.
5.Connect network agian.
6.Try to continue video playing or refresh the page.
[3.Expected Result]:
6.Can continue video playing after network recover.
[4.Actual Result]:
6.Can't continue playing,if we refresh the page,blank page displayed.
[5.Reproduction build]:
Flame 2.1 build:
Gaia-Rev 1b231b87aad384842dfc79614b2a9ca68a4b4ff3
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/95fbd7635152
Build-ID 20141119001205
Version 34.0
[6.Reproduction Frequency]:
Always Recurrence,2/2
Free Test
| Reporter | ||
Comment 1•11 years ago
|
||
| Reporter | ||
Updated•11 years ago
|
status-b2g-v2.1:
--- → affected
Comment 3•11 years ago
|
||
Hi Alissa, please also check if v2.2 has this issue or not.
If v2.2 also has this problem, you can set blocking-b2g: v2.2? directly
Flags: needinfo?(mlien) → needinfo?(huayu.li)
| Reporter | ||
Comment 4•11 years ago
|
||
Hi,mike
This issue not exist on v2.2
status-b2g-v2.2:
--- → unaffected
Flags: needinfo?(huayu.li) → needinfo?(mlien)
Comment 5•11 years ago
|
||
this is v2.1 specific, set blocking-b2g: v2.1?
blocking-b2g: --- → 2.1?
Flags: needinfo?(mlien)
Comment 6•11 years ago
|
||
QA can you please help reproduce this on 2.0 ? Want to confirm if this is a real regression. Also, can you please stick in the build id for 2.2 that you tested on ?
Flags: needinfo?(huayu.li)
Keywords: qawanted
Comment 7•11 years ago
|
||
(In reply to bhavana bajaj [:bajaj] from comment #6)
> QA can you please help reproduce this on 2.0 ? Want to confirm if this is a
> real regression. Also, can you please stick in the build id for 2.2 that you
> tested on ?
Issue DOES occur in Flame 2.0
Actual Results: Disabling data network connection during video playback, then refreshing the webpage, results
in a blank screen.
Video URL:
http://youtu.be/wGF0BfAdg_Q
Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141222000200
Gaia: ce83ea7b8e3fa2d1c3fd771fc22b654c18b3c381
Gecko: 752225b5d185
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
--------------------------------------------------
--------------------------------------------------
Issue DOES NOT occur in the following Flame 2.2 build:
Device: Flame 2.2 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141222040204
Gaia: ca6e91e09ef3ab417a0f6b6d6668d43597d85700
Gecko: b915a50bc6be
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 37.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
Flags: needinfo?(huayu.li) → needinfo?(jmitchell)
Keywords: qawanted
Updated•11 years ago
|
QA Contact: ddixon
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ddixon
:daleharvey, could you please take a look at this issue?
Flags: needinfo?(dale)
Whiteboard: [systemsfe]
Comment 9•11 years ago
|
||
I would need some guidance from media to figure out how to fix this, if someone from media could take a look that would be really helpful, thanks
Flags: needinfo?(dale) → needinfo?(cpearce)
Comment 10•11 years ago
|
||
This bug probably needs attention from someone on the FxOS media team; ni? slee.
Someone probably needs to step through ChannelMediaResource and/or the MediaCache/ChannelMediaStream code and follow through what happens when the connection drops.
In theory, we should be able to reproduce this same issue on desktop by just disabling your WiFi connection in the middle of streaming a video, or pulling out the ethernet cable.
Flags: needinfo?(cpearce) → needinfo?(slee)
Comment 11•11 years ago
|
||
I tried 2.1 and found that only Youtube has problem. Here is the log. My flow is
1. connect to youtube
2. disable wifi then enable wifi
3. refresh the page
3.1 youtube cannot connect again and I got some errors from logcat
3.2 connect to other sites and there is no problem
4. restart browser app and connect to youtube. It works fine.
Flags: needinfo?(slee) → needinfo?(dale)
Comment 12•11 years ago
|
||
Given this does not happen in 2.2, is there a simple lowrisk workaround or uplift we can do to avoid shipping with this in 2.1 ? dale, would you know here or who is it that I can NI to help investigate this ?
Comment 13•11 years ago
|
||
Alissa, can you confirm there is no way to recover via reload or restarting the app(which is worse) etc? Can we also try this issue on desktop to see if we can reproduce this there?
Dale, Could this be a youtube issue?
Flags: needinfo?(huayu.li)
Keywords: qawanted
Comment 14•11 years ago
|
||
Since this is not impacting v2.2, is it possible to ask for a reverse regression range to see what fixed this? Once we know that we should be able to determine the risk of an uplift.
Note: we'll need a reverse range here, looking for the commit which *fixed* this.
Keywords: regressionwindow-wanted
Updated•11 years ago
|
QA Contact: jmercado
Comment 15•11 years ago
|
||
It should be noted that even on builds that are "working" the user cannot restart playback and must refresh the page instead. I'm finding the window for at what point refreshing the window was fixed, but the other issue still occurs and seems far more user unfriendly by being the cause of wanting to refresh in the first place.
Environmental Variables:
Device: Flame 3.0
BuildID: 20150114071217
Gaia: ce6c9b72d863c80c842c65acf3b040baf4901a97
Gecko: 3121f461b090
Version: 38.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0
Comment 16•11 years ago
|
||
Somehow flipped those flags opposite of how I intended and removed the wrong keyword...
| Reporter | ||
Comment 17•11 years ago
|
||
(In reply to bhavana bajaj [:bajaj] from comment #13)
> Alissa, can you confirm there is no way to recover via reload or restarting
> the app(which is worse) etc? Can we also try this issue on desktop to see if
> we can reproduce this there?
1.After network connected agian,we cannot reload current video.so it is same on 2.1,2.2,mac.
2.If we relaunch browser after step6 on 2.1,we can play video agian.
3.We do same step(1-6) on mac,after refresh page,we can get normal page agian,so it is same result on2.2 and mac,but it failed on 2.1.
Flags: needinfo?(huayu.li)
Comment 18•11 years ago
|
||
Based on comment 11, this is possibly an evangelism bug? Would need someone to dig into the logcat errors as mentioned in that comment. Unfortunately I'm not sure if I'll have time to do this soon.
Flags: needinfo?(kgrandon)
Comment 19•11 years ago
|
||
Bug 880997 might have fixed the refresh issue.
Mozilla-inbound Regression Window
Last Broken
Environmental Variables:
Device: Flame 2.2
BuildID: 20140905191502
Gaia: c7de02ef1e0ad97d86e5bbef2d19828a236aea27
Gecko: 0ab9f81811c6
Version: 35.0a1 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
First Working
Environmental Variables:
Device: Flame 2.2
BuildID: 20140905200201
Gaia: c7de02ef1e0ad97d86e5bbef2d19828a236aea27
Gecko: 2092f7bd26d2
Version: 35.0a1 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Last Broken gaia / First Working gecko - Issue does NOT occur
Gaia: c7de02ef1e0ad97d86e5bbef2d19828a236aea27
Gecko: 2092f7bd26d2
First Working gaia / Last Broken gecko - Issue DOES occur
Gaia: c7de02ef1e0ad97d86e5bbef2d19828a236aea27
Gecko: 0ab9f81811c6
Gecko Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0ab9f81811c6&tochange=2092f7bd26d2
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
Comment 20•11 years ago
|
||
Boris, can you look at this bug please? It looks like this was fixed by the work done on bug 880997
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(bzbarsky)
Comment 21•11 years ago
|
||
I'm not sure what you want to me to look at, exactly. The fix for bug 880997 _could_ have changed behavior of some sites that were using the IDL attribute, I guess, depending on what they're doing with it...
Flags: needinfo?(bzbarsky)
Comment 22•11 years ago
|
||
Given this isn't a regression in 2.1 and is also fixed in 2.2 I am clearing the nom..
blocking-b2g: 2.1? → ---
Comment 23•11 years ago
|
||
Clearing needinfo and closing as its fixed
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dale)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•