You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the following example you'll see that the existence of otherRef prevents the socketRef's cleanup from being executed. This is made more evident by assigning socketRef a systemId.
Expected result
No errors and the cleanup function of socketRef to be executed.
Actual result
An error: Actor with system ID 'next' already exists.
Cleanup function isn't called, which is evident by the logs.
rostero1
changed the title
Bug: callback actor isn't getting cleaned up when another actor is spawned
Bug: [v5] callback actor isn't getting cleaned up when another actor is spawned
Jun 16, 2023
Description
In the following example you'll see that the existence of
otherRef
prevents the socketRef's cleanup from being executed. This is made more evident by assigning socketRef a systemId.Expected result
No errors and the cleanup function of socketRef to be executed.
Actual result
Reproduction
https://stackblitz.com/edit/stackblitz-starters-u8lam3
Additional context
No response
The text was updated successfully, but these errors were encountered: