-
Notifications
You must be signed in to change notification settings - Fork 87
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
Always use persistent handles when passing dart objects as userdata to callbacks #1491
Conversation
Pull Request Test Coverage Report for Build 7660137927
💛 - Coveralls |
I have not added new unit tests for this, as it needs to run fairly long in order to provoke it, and in most cases it will hang the notifications instead of crashing the process. But the re-production code is in the issue #1492. |
683260d
to
07c7063
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good - is there a way to run a test to see if we leak any resources with this change? (I don't think we should but it's the kind of change that carries this risk)
We could look into using the Or perhaps better to use the fairly new leak_tracker package I have created a separate issue for that #1494 |
Fixes: #1492