-
Notifications
You must be signed in to change notification settings - Fork 36
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
Assertion error at startup #23
Comments
Sometimes this error also manifests as a segfault ( |
Other times it just hangs on startup, without the process ever coming fully alive (in this case, the API never starts listening). |
Hi, thanks for the report. Can you try the new 0.3.2 release and see if that fixes it? It has a bugfix for a problem that sounds similar to yours. |
Hey, new errors now:
The program I'm using this with uses tokio btw. |
Get the same error on Rust 1.65 on x86 Mac |
This is an odd one: I've seen it my M1 Mac as well and the source of the message is almost certainly this. That implies that something is trying to update information associated with a thread, but the thread already has associated information, so it asserts and fails. I can't reproduce it reliably. I've only seen it happen a handful of times in the last couple of months. AFAICT, that code only runs during thread creation, so I'm not sure why it's being triggered. I don't think this helps much, but maybe it points a way to investigate what is happening. |
Can repro on 0.3.2 on an M1, macOS 13.1, rust 1.66.0. It triggers for me when I run That it's reproducible on x86 probably rules out my pet theory, which would be that it's related to time resolution on apple silicon. |
Running tokio after dhat should fix this problem: fn main() {
//#[cfg(feature = "dhat-heap")]
let _profiler = dhat::Profiler::new_heap();
main2();
}
#[tokio::main]
async fn main2() {
println!("Hello, world!");
} Unfortunately I can't figure out where the rabbit hole is 😞 |
Repro
Get repo, checkout appropriate branch:
Run this command:
Output: https://gist.github.com/banool/a3aa22bfcf9154c15bc2073306d4fe9c.
This error does not occur with the default allocator / jemalloc.
Details:
The text was updated successfully, but these errors were encountered: