You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 cargo build --release is causing the crash or running the program built with opt-level=3 is causing the crash ?
@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.
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.
Activity
9prady9 commentedon May 31, 2021
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
cargo build --releaseis causing the crash or running the program built withopt-level=3is causing the crash ?BA8F0D39 commentedon Oct 5, 2021
It seems jemalloc isn't compatible with arrayfire
#[global_allocator]
static ALLOC: jemallocator::Jemalloc = jemallocator::Jemalloc;
9prady9 commentedon Oct 6, 2021
@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.
9prady9 commentedon Dec 23, 2021
Sorry, couldn't get back to this. Will try this weekend.
9prady9 commentedon Feb 19, 2022
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.
9prady9 commentedon May 9, 2022
Closing due to inactivity @BA8F0D39 feel free to re-open if you still have the issue reported or more info to share.