-
Notifications
You must be signed in to change notification settings - Fork 58
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
[BUG] Rust compiler optimizations crashes arrayfire #299
Comments
Can you also please update the description with details like OS, ArrayFire(installed library) version, ArrayFire crate version, Backend being used, GPU driver version. To get some clarification, just compiling |
It seems jemalloc isn't compatible with arrayfire #[global_allocator] |
@BA8F0D39 I assume, you are referring to the CPU backend because it should not be a problem for CUDA/OpenCL except in few minor set of APIs where host side allocations take place for strings etc. I haven't used jemalloc, so I would have to try it and check where the incompatibility stems from. Is it the upstream lib or something in rust crate. I suspect it could be upstream lib but cannot be certain about it yet. |
Sorry, couldn't get back to this. Will try this weekend. |
can you please tell how do I reproduce this on my end ? perhaps your stand alone code from your project that uses jemalloc. Just the opt-level(3) and --release flag definitely aren't the problem as you have already pointed that out and I was able to run examples with those settings. Graphics examples are not working on my current system, but I don't think these are related. |
Closing due to inactivity @BA8F0D39 feel free to re-open if you still have the issue reported or more info to share. |
Description
Similar to bug #73 , rust compiler optimizations create instability the program and will result in a crash
Setting compiler optimizations to the highest level
and building a rust program in release mode
crashes my program and GPU drivers.
Hilariously, my screen turned blank and I didn't get to see the error message.
The text was updated successfully, but these errors were encountered: