1586853 - Stuck partial wake locks (background) in FennecAndroid 68.1.1

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Marcia Knous [:marcia]]

While perusing the Google Play Console, I noticed an alert that Fennec release is in the bad behavior threshold for stuck partial wake locks. Previously I had filed Bug 1571781 for a similar issue. Some of the wake lock tags seem related to audio.

Adding Petru so he maybe can take a look when he gets a chance, since he looked at the previous issue I reported.

Comment 1

[Marcia Knous [:marcia]]

I see this is still happening in the GPC when I looked today.

Comment 2

[Marcia Knous [:marcia]]

This issue is back again in both 68.2.1 and 68.3.0. We have an overall issue with stuck partial wake locks as well as an an anomaly which was detected on 12/24.

Heavy concentration of Samsung phones at the top of the device list.

Comment 3

[Andrei Lazar]

After some research I found out that:

• top offenders are: AudioMix, AudioIn which are system wakelocks
• the threshold is 0.10% and the peak was ~0.04%
• we have tags which do not appear in the Vitals section of Google Play Store

I propose to close this as won't fix, but please let me know how do you want to proceed further.

Comment 4

[Marcia Knous [:marcia]]

(In reply to Andrei Lazar from comment #3)

After some research I found out that:

• top offenders are: AudioMix, AudioIn which are system wakelocks
• the threshold is 0.10% and the peak was ~0.04%
• we have tags which do not appear in the Vitals section of Google Play Store

I propose to close this as won't fix, but please let me know how do you want to proceed further.

I am fine with closing if this isn't something we feel we should worry about. If we have tags which don't appear in the Vitals section, should they be added?