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
To restate the problem, the issue is that Nim's ORC tracking of each memory graph is thread-local, so moves across threads leave such references in a bogus state should they be collected in a "foreign" thread...
Orc crashes when a Continuation (or any ref object) passed through the queue reaches the end of its life span and the final
=destroy
is run.This is evident by incrementing the ref count of an object by 1 before the end of its lifespan and comparing the behaviour before and after.
ARC does not share this issue; the final
=destroy
can be called without issue and the memory is collected appropriately.The text was updated successfully, but these errors were encountered: