Fixed
Status Update
No update yet.
Comments
ap...@google.com
We are currently using AGP internal task types to flag memory-intensive tasks to enforce a reduced parallelism at execution time. I've raised this separately (with a lot more detail) as a feature request (
Description
Component used: Activity Version used: 1.2.0-alpha07
If you register for a result with a
LifecycleOwnerand your activity goes through process death and restoration, once it is created again if there is already result a waiting to be returned to theLifecycleOwneran observer is added to wait until theLifecycleisSTARTED. When the lifecycle owner is unregistered, the observer is never removed.We should keep track of any observers added to the
LifecycleOwnerand remove them if the callback for the lifecycle owner is ever unregistered.