Closed Bug 1019973 Opened 6 years ago Closed 5 years ago
[B2G][Tarako][Facebook] Receiving an incoming call while in the app will leave user on homescreen when ended
Description: Receiving an incoming call while in the Facebook app will leave the user on the device homescreen after the call ends rather than where they were in the app before the call took place. Seems to happen more frequently if the user is performing an action in the app (ex: has the messages drop-down window open) and when the call is denied rather than answered. Repro Steps: 1) Update device to BuildID: 20140602014001 2) Install and launch Facebook from the marketplace 3) Tap the messages icon to open the drop down window 4) Call the DUT from another device 5) Deny the incoming call on the DUT Actual: User can be deposited on the device homescreen rather than their starting point in the Facebook app after receiving a call. Expected: User is returned to their starting point after the call ends. Environmental Variables: Device: Tarako 1.3T BuildID: 20140602014001 Gaia: 335486c42498fa7a93c21e4d6121199728602ab8 Gecko: 55e4d83019e5 Version: 28.1 Firmware Version: SP6821a-Gonk-4.0-4-29 Notes: Repro frequency: 40% See attached: Video, logcat
Qwanted for results on Buri v1.3 or will post in the morning.
This issue also occurs on the Buri v1.3 MOZ ril. Environmental Variables: Device: Buri v1.3 MOZ BuildID: 20140529024024 Gaia: 5bd226b03a2d63dfe9df204f7c0afb9984e8fd42 Gecko: 42ef074f380f Version: 28.0 RIL Version: Firmware Version: v1.2-device.cfg User can be deposited on to the homescreen instead of back in app.
I think it might be a LMK. Rachel, can we get the logcat please?
Sorry about that! Attaching.
From logcat: 06-05 10:28:50.400: E/OomLogger(85): [Kill]: lowmem_shrink select 1697 (Facebook), adj 10, size 10800, to kill 06-05 10:28:50.400: E/OomLogger(85): [Kill]: lowmem_shrink send sigkill to 1697 (Facebook), adj 10, size 10800
Whiteboard: [tarako-exploratory] → [tarako-exploratory][memshrink]
Whiteboard: [tarako-exploratory][memshrink] → [tarako-exploratory][MemShrink:P2]
This doesn't occur on master and 1.3T is no longer supported, so I'm resolving this. We would still benefit from work on bug 1042576, though.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.