Lingering object references from event graph pins
Not sure if this is a bug as such, but it's rather hidden and definitely has potential to cause issues.
I was trying to find out why one of my objects was not being destroyed when I expected it to be. Using the
I can see to an extent why this is the case, since execution flow in an event graph can contain nodes such as Delay, meaning pin lifetime isn't as simple as on a function call stack. Still, it seems like there should be a way to detect the end of an execution path and destroy all pin contents along that path. As things are, a large asset could remain in memory indefinitely even if all other references were nulled, just because it was returned from a node which was executed once.
asked Feb 06 '16 at 08:21 PM in Everything Else
Follow this question
Once you sign in you will be able to subscribe for any updates here