I’m fairly new to numba and my usage has been around JIT compilation until recently. I have been tasked with taking JIT functions and moving them to AOT compilation to save on warm up time. I’m able to get some custom types implemented into the AOT functions using the interval type example and this works for the most part. Where it fails is when a custom type contains an attribute that is a NumPy array and the value is an array the was created inside the AOT compiled function. I have created an example repo here that demonstrates the issue. Although, the Github action isn’t working, I’m able to see the issue on my local machine running MacOS Intel. I will often see an Abort trap: 6 error, but sometimes the function will return incorrect values, usually all zeros. A coworker runs an arm64 Mac and normally sees a double free error. Feels like the boxing is wrong for these or maybe the newly created array is derefenced somewhere?
I know pycc is being deprecated, but I’m hoping this is already supported and I’m just implementing something wrong. Appreciate any help!