Leak (?) when using object member in a RunnableSequence #30587
Replies: 1 comment
-
I'm moving this into an issue because I'm pretty sure it's a bug |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Checked other resources
Commit to Help
Example Code
Description
Hi, we encountered a memory leak in our app and simplified it down to this. When creating a new
RunnableSequence
where a member of an object (thing.call
) that invokes aRunnable
is followed by something else like aRunnablePassthrough
, the memory is not cleaned up.There seems to be a reference to
thing
still held somewhere which is why the GC doesn't remove the object from memory.Output:
In our real app, we were able to work around it by creating two
Runnable
s, the first with the object member and the second with further steps, and invoking them one after the other.Is this expected and we're using it wrong or is it a bug? Thank you!
System Info
System Information
Package Information
Optional packages not installed
Other Dependencies
Beta Was this translation helpful? Give feedback.
All reactions