Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SegFault when a lot of Nodes are freed. #78

Open
CedNaru opened this issue Feb 27, 2021 · 0 comments
Open

SegFault when a lot of Nodes are freed. #78

CedNaru opened this issue Feb 27, 2021 · 0 comments

Comments

@CedNaru
Copy link
Member

CedNaru commented Feb 27, 2021

This one is a tricky issue.

When nodes have been freed from memory, our plugin just automatically detects when it happens and detaches the listeners/events. by the mean of is_instance_valid.
Usually it's enough, but when a big chunk of memory has been freed, we literally no longer can access the address to the node and get a segfault.

The simple solution for it, should to connect to the signal tree_exited so we can detach node at this moment instead of checking the pointer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant