Emergency Self-Construct
Emergency Self-Construct
> It seems a little weird to me, that while `typed.List` is allowed by the compiler as value as per @esc's example > > ```python > @numba.njit > def f():...
@allai5 @njriasan thank you for bringing this up. I presume #8305 will fix?
@CHELOBV thank you for submitting this. I have started to triage this issue. I downloaded the file `test.npy`, however, when running the code I receive the error: ``` 💣 zsh»...
After installing `geojson` I ran the supplied reproducer and data: ``` 💣 zsh» python issue_7890.py Now 3.314018249511719e-05 0.21585464477539062 [16] [ 3 15] [ 3 15] [ 2 14] [0 1]...
Also, this came back with: ``` 💣 zsh» echo $? 134 `` Which would indicate that program received a `SIGABRT`.
After running this with `boundschecking=True` I received yet another error message: ``` 💣 zsh» python issue_7890.py Now 3.409385681152344e-05 0.18205642700195312 [16] [ 3 15] [ 3 15] [ 2 14] [0...
I debugged this some more, and found that the array may in fact be an object array. I don't think that Numba supports object-arrays very well. ``` In [3]: numpy.load("test.npy",...
@CHELOBV you mentioned, that this does happen sometimes only? For me, the code and array crash reproducibly every time.
So far I was on 3.9 on OSX Catalina on x86_64, now, switching to 3.10 on Linux x86_64, I get: ``` 💥 zsh» python issue_7890.py Now 4.206834316253662 dog [16] [...
So, I don't really understand the code very well, unfortunately, but I did manage to eliminate the segfault: By commenting out the line `paths_update.remove(path)` on line 102, I can get...