Wakelocks held by a client not released if client quits/crashes
Bug #1409722 reported by
Gerry Boland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
powerd |
New
|
Undecided
|
Ricardo Mendoza |
Bug Description
While testing:
https:/
which acquires a wakelock to ensure app management tasks complete ok, I noticed that the only time a wakelock is actually released is if the client itself explicitly releases it.
If the powerd client crashes, or fails to explicitly release the wakelock itself on exit, the wakelock will be held perpetually.
Suggest that Powerd listens for dbus disconnect signals of clients that acquire a wakelock, and release the wakelock automatically, to robustify against bad clients.
To post a comment you must log in.