NPE on checking wake locks [123835104]

Fixed

Bug

Status Update

No update yet.

Description

ru...@gmail.com

created issue #1

Feb 4, 2019 03:03PM

Component used: WorkManager
Version used: 1.0.0-beta03
Devices/Android versions reproduced on: couldn't reproduce

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.os.PowerManager$WakeLock.isHeld()' on a null object reference
at androidx.work.impl.utils.WakeLocks.checkWakeLocks(WakeLocks.java:89)
at androidx.work.impl.background.systemalarm.SystemAlarmService.onAllCommandsCompleted(SystemAlarmService.java:69)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.dequeueAndCheckForCompletion(SystemAlarmDispatcher.java:217)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$DequeueAndCheckForCompletion.run(SystemAlarmDispatcher.java:317)
at android.os.Handler.handleCallback(Handler.java:810)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:189)
at android.app.ActivityThread.main(ActivityThread.java:5529)
at java.lang.reflect.Method.invoke(Method.java)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:950)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:745)

Seems like the copy of wake locks can contain null keys. I couldn't reproduce this, but some devices on crashlytics are reporting this crash.

Comments

ap...@google.com <ap...@google.com> #2Feb 4, 2019 07:26PM

Any update on this? The issue makes really hard to use AVD even completely unusable sometimes.
I enabled the "show taps" feature on developer options. I can see that touching is stuck sometimes. Multiple finger touch solves it by resetting but not always.

ru...@gmail.com <ru...@gmail.com> #3Feb 4, 2019 07:39PM

Hi mustafiran@, thanks for reporting this issue. This bug has been fixed by this CL. But it seems like we didn't cherry-pick the fix to the stable release branch. To unblock yourself immediately, you could try to use the latest canary release. I will make sure the stable release has the fix and goes out ASAP.

su...@google.com <su...@google.com> Feb 4, 2019 08:31PM

Marked as fixed, reassigned to su...@google.com.

ru...@gmail.com <ru...@gmail.com> #4Feb 5, 2019 09:37AM

The fix will be available in 31.3.10 beta release for emulator.

su...@google.com <su...@google.com> #5Feb 5, 2019 05:38PM

Hi,

I can't see 31.3.10 version here

https://developer.android.com/studio/emulator_archive
How will it take to get the stable version release?

Regards

<buganizer-system@google.com> adresine sahip kullanıcı 8 Tem 2022 Cum,
20:23 tarihinde şunu yazdı:

- Show quoted text -

--
-----------------------------------------------------

mustafairan.wordpress.com

Issue 123835104