Closed Bug 1201986 Opened 9 years ago Closed 9 years ago

[Window Mgmt] The viewfinder will be frozen when using the camera option for a SMS attachment

Categories

(Firefox OS Graveyard :: Gaia::Camera, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master affected)

RESOLVED WORKSFORME
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- affected

People

(Reporter: KTucker, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [2.5-Daily-Testing])

Attachments

(1 file)

If the user adds a contact to the recipient field, taps on the attachment icon in a message and then selects camera, they will notice that the viewfinder is frozen.

Repro Steps:
1) Update a Flame to 20150903150222
2) Tap on the "Messaging" icon.
3) Tap on the "Compose New Message" icon.
4) Add a saved contact to the recipient field. 
5) Tap on the "Attachment" icon and select "Camera"
6) Observe the viewfinder. 

Actual:
The viewfinder will be frozen.

Expected:
The viewfinder works as expected. 

Environmental Variables:
Device: Flame 2.5 (Full Flash)(KK)(319mb)
Build ID: 20150903150222
Gaia: d7385b79e68d4ad662cacf810506e9ee53345d23
Gecko: 7f987c38bd3e5ac9a834981e85378bdb02338e9d
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Repro frequency: 5/5 100%
See attached: video clip, logcat
This issue does not occur on Aries 2.5 and Flame 2.2 

The viewfinder is not frozen when using the camera option when attaching an image to a SMS.

Device: Aries 2.5
Build ID: 20150904150055
Gaia: 85ae6808d298a4010aaab341c66699f1b87eec9c
Gecko: 691b1524602d12afc2336474d8ddd4eff1476c4d
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Device: Flame 2.2 (Full Flash)(KK)(319mb)
Build ID: 20150903183008
Gaia: 335cd8e79c20f8d8e93a6efc9b97cc0ec17b5a46
Gecko: d3cb4f28c735
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Whiteboard: [2.5-Daily-Testing]
[Blocking Requested - why for this release]:

Broken functionality and a regression.
blocking-b2g: --- → 2.5?
Flags: needinfo?(jmercado)
If you are having trouble reproducing this issue restart the phone and follow the steps above.
QA Contact: ddixon
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Blocking for 2.5, P2 priority.
blocking-b2g: 2.5? → 2.5+
Priority: -- → P2
Mozilla Inbound Window

Last Working 

Device: Flame Master
BuildID: 20150902054523
Gaia: e2fab8f6ac345ecde10a1350e699be9ceb6987d6
Gecko: 127672f1e70d495a1ff0b5222d7047f2c97d3ba2
Version: 43.0a1 (Master) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

First Broken 

Device: Flame Master
BuildID: 20150902055426
Gaia: e2fab8f6ac345ecde10a1350e699be9ceb6987d6
Gecko: e110acdf8e64125af01ace9800f593814ce021e1
Version: 43.0a1 (Master) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Last Working Gaia and First Broken Gecko
Issue DOES occur here: 
Gaia: e2fab8f6ac345ecde10a1350e699be9ceb6987d6
Gecko: e110acdf8e64125af01ace9800f593814ce021e1

Last Working Gecko and First Broken Gaia
Issue DOES NOT occur here: 
Gaia: e2fab8f6ac345ecde10a1350e699be9ceb6987d6
Gecko: 127672f1e70d495a1ff0b5222d7047f2c97d3ba2

Mozilla Inbound Pushlog (Gecko):
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=127672f1e70d495a1ff0b5222d7047f2c97d3ba2&tochange=e110acdf8e64125af01ace9800f593814ce021e1

Possible Cause: 

Bug 1200099 - Eliminate HTMLMediaElement::mPlaybackStream
Blocks: 1200099
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Robert this issue seems to have been caused by the changes made for bug 1200099.  Can you please take a look?
Flags: needinfo?(jmercado) → needinfo?(roc)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Sounds like it could be related to bug 1201969. Let's see what happens there?
Depends on: 1201969
Flags: needinfo?(roc)
Can we QA this again now that bug 1201969 landed?
Keywords: qawanted
I was able to reproduce this issue on my 4th attempt on Flame 2.5

The viewfinder froze when selecting the camera option for attaching a picture in SMS.

Device: Flame 2.5
BuildID: 20150911030227 (Full Flash)(KK)(319mb)
Gaia: 6280500a6cb8d1b178cdd163450e36d22846fbed
Gecko: c0abc2a6e11f52761366e029eb1bae4c9864a8a3
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
Component: Gaia::System::Window Mgmt → Audio/Video
Product: Firefox OS → Core
Alastor,
Per comment 18, can you have a look?
Flags: needinfo?(alwu)
Hi, KTucker,
Could you help me verify whether this issue have been solved in latest m-c?
Because I can't reproduce it at following buildID - 20150915141648.
Thanks.
Flags: needinfo?(alwu)
Keywords: qawanted
After about 10 attempts I was able to repro this issue once on Flame 2.5.
Result: Viewfinder became frozen.

Environmental Variables:
Device: Flame 2.5 Kk Full flash (319mb)
Build ID: 20150915193016
Gaia: 994ff1537c2d7ca4d1658806c50f3ceba1053f9b
Gecko: 3e8dde8f8c174cce2c0b65c951808f88e35d1875
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
I still can't reproduce this issue in following testing environments.
Is any possible the firmware issue?

Environmental Variables:

[Flame 2.5 Kk]
Gaia-Rev        01cf74daf8e1c1fbc945dd61ff0b2524f4b06b8e
Gecko-Rev       262451:c69e31de9aec
Build-ID        20150916181705
Version         43.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  75
FW-Date         Tue Jan  6 12:24:47 CST 2015
Bootloader      L1TC100118D0


[Aries 2.5KK]
Gaia-Rev        250c2dfa9cd6eb6ce5b7162e5f53a3b6a33c3aef
Gecko-Rev       3a3b80f18175a053d86c9adbe74909dcaa9c184c
Build-ID        20150916104746
Version         43.0a1
Device-Name     aries
FW-Release      4.4.2
FW-Incremental  eng.worker.20150616.234403
FW-Date         Tue Jun 16 23:44:13 UTC 2015
Bootloader      s1
Or you have any other preprocess before the reproduce steps?
Per STR request in comment 15, mark qawanted.
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage+]
QA Contact: ddixon → pcheng
1. This issue appears to be Flame only. It is possible that it also happens on Aries, just with extremely low repro rate, but we haven't been able to reproduce it on Aries.

2. As comment 10 and comment 13 stated, the repro rate on Flame could be low as well.

3. Comment 3 stated if this doesn't repro, reboot the phone. Did you reboot the phone between each attempt?

4. We have been testing Flame on v18D v4 base. And 319MB memory.

I reproduced this issue on today's Flame nightly 3 out of 6 attempts, with rebooting the phone between each attempt. The steps are simply following STR, with a prerequisite of creating a contact in contacts app.

Tested on:

Device: Flame (319MB memory)
BuildID: 20150921073455
Gaia: 2d370fa35c1a0ee2a637e3772c0843586a5f96c9
Gecko: 039a8490891595736b16a3ccb17f025f4dcf13eb
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5 Master) 
Firmware Version: v18Dv4
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
(In reply to Pi Wei Cheng [:piwei] from comment #17)
> 1. This issue appears to be Flame only. It is possible that it also happens
> on Aries, just with extremely low repro rate, but we haven't been able to
> reproduce it on Aries.
> 
> 2. As comment 10 and comment 13 stated, the repro rate on Flame could be low
> as well.
> 
> 3. Comment 3 stated if this doesn't repro, reboot the phone. Did you reboot
> the phone between each attempt?
> 
> 4. We have been testing Flame on v18D v4 base. And 319MB memory.
Do you mean you only tested on 319MB memory?
If yes, could you test on 512MB memory?
Flags: needinfo?(pcheng)
QAwanted to address comment 18
Keywords: qawanted
This issue is still reproducible on Flame 512MB. I reproduced it on the second attempt, but could not repro it on all subsequent attempts including rebooting or reflashing the phone. the total repro rate is 1 out of ~20. The repro rate seems to have dropped in higher memory setting.

Device: Flame 2.5 (512MB memory)
BuildID: 20150929030205
Gaia: f345f6a015709beeb2ca3955cab077fcaa959d3b
Gecko: acdb22976ff86539dc10413c5f366e1fb429a680
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5) 
Firmware Version: v18Dv4
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(pcheng) → needinfo?(jmercado)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
Component: Audio/Video → Gaia::Camera
Product: Core → Firefox OS
Andrew -- I'm not sure if this is a bug in the camera code or the playback code.  Can you look at this and assess if you think this is likely in the camera code or not?  If not, can you move it to Core::Audio/Video::Playback?   Thanks
Flags: needinfo?(aosmond)
This sounds similar to bug 1202967. It appears to have been fixed in gaia, but I wonder if we are hitting the same problem via a different code path. I don't think this is camera but unfortunately I have been unable to reproduce in any memory configuration (including 319MB) with the following build:

Build ID               20151013030230
Gaia Revision          d400cda6bf0f8b30dcf7d7d71bfa61f29a3f1588
Gaia Date              2015-10-13 06:42:17
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/607a236c229994df99766c005f9ec729532d7747
Gecko Version          44.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20151013.083726
Firmware Date          Tue Oct 13 08:37:39 EDT 2015
Bootloader             L1TC000118D0

If this is still reproducible by somebody, please try with extra camera/media logging turned on. To enable, do the following:

adb remount
adb pull /system/bin/b2g.sh .
edit and add the following line near the top of the file (all one line):

export NSPR_LOG_MODULES=nsMediaElement:6,nsTrackElement:6,nsMediaElementEvents:6,MediaStreamGraph:6,MediaDecoder:6,MediaManager:6,TrackUnionStream:6,OmxDecoder:6,Camera:6

adb push b2g.sh /system/bin
adb shell chmod 755 /system/bin/b2g.sh
adb reboot
Flags: needinfo?(aosmond)
Keywords: qawanted
We could no longer reproduce this issue after 60+ attempts on the Flame 2.5

The viewfinder did not freeze up.

Device: Flame 2.5 (Full Flash)(KK)(319mb)
Build ID: 20151013030230
Gaia: d400cda6bf0f8b30dcf7d7d71bfa61f29a3f1588
Gecko: 607a236c229994df99766c005f9ec729532d7747
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

I think it is safe to close this out for now. We will reopen this issue if it is encountered again.
Status: NEW → RESOLVED
Closed: 9 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
Resolution: --- → WORKSFORME
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: