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

Unoptimized stdtest sometimes causes jemalloc assertion error #22710

Closed
klutzy opened this issue Feb 23, 2015 · 2 comments
Closed

Unoptimized stdtest sometimes causes jemalloc assertion error #22710

klutzy opened this issue Feb 23, 2015 · 2 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc

Comments

@klutzy
Copy link
Contributor

klutzy commented Feb 23, 2015

(Using Rust rev dcc6ce2)

$ ../configure --disable-optimize

...

$ stdtest-x86_64-pc-windows-gnu.exe sync::mpsc
...
<jemalloc>: C:/home/stone/rust/src/jemalloc/include/jemalloc/internal/tsd.h:502:
Failed assertion: "tsd->state == tsd_state_reincarnated"

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Not sure if it's related to #22628 or not. Also not sure if it only occurs with no-opt option.

@steveklabnik steveklabnik added the A-testsuite Area: The testsuite used to check the correctness of rustc label Feb 23, 2015
@steveklabnik
Copy link
Member

Over a year later, with no comments. @klutzy are you still seeing this?

@klutzy
Copy link
Contributor Author

klutzy commented Mar 6, 2016

Not producible. It was a supposed bug of low-level thread/network binding and I guess it had been fixed ago.

@klutzy klutzy closed this as completed Mar 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Projects
None yet
Development

No branches or pull requests

2 participants