-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Channels leak when sent over channels #763
Comments
I'm guessing this is leaking the |
https://gist.github.com/1112731 Same test case. New syntax. |
I think probably recv isn't calling drop on the value it's receiving into. In the following test case, if you uncomment the commented line it no longer leaks.
|
This makes it possible to create rlibs for any target without installing a toolchain for the target Fixes rust-lang#763
* Handle non-strict select * Fix non-strict phi
* Add --enable-unstable option Unstable options now require users to explicitly enable them. This is important because the unstable options can be unsound or give spurious CEX. * Disable spurious pointer checks by default We have been seeing a lot of spurious CEX related to pointer out of bounds checks in arithmetic operations. It is actually valid rust in some cases, and we can't differentiate the valid ones from the invalid ones today. Thus, I'm disabling them by default. Note that dereferencing invalid pointers is caught by different checks and they should not be affected by this change. This changes fixes rust-lang#563 and rust-lang#763. Co-authored-by: Zyad Hassan <88045115+zhassan-aws@users.noreply.github.com>
Minimal-ish test case:
https://gist.github.com/1110969
If I reduce it further, it seems to either not reproduce or it will deadlock or it will crash. Hopefully all the same cause!
The text was updated successfully, but these errors were encountered: