-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Segmentation fault in GC #27952
Comments
Are you able to provide steps that reproduce this? |
Unfortunately, no. It occurred after a long line of computation triggered after some REPL work. Sorry. |
I managed to produce a repeatable series of steps to generate this error. My environment:
I ran:
And then:
The output is (to get to this point takes several minutes):
|
The crash does not appear to be related to the number of threads. The same error is reported when I force the number of threads to be 1. |
FWIW, it ran successfully on my Mac with julia-beta:
|
I suspect this issue is really an instance of this bug. |
Can you check if the fix for #27955 fixed this one also? |
EDIT: This might be the same issue.
|
Also try rebuilding llvm ( |
Probably ideally wait until #28362 is merged first. |
Now worth checking this again. |
I tried with Commit a83dfee (Windows 10).
|
We had just merged another one of these when @JeffBezanson, so please try with a more recent version. |
E.g. the new 0.7.0-rc2 that was just tagged (no binaries yet, so you'll have to build it). |
Can I get a binary with this change implemented? I'm on the road and I cannot build it myself. |
I encountered a similar failure during build.
julia version |
This was with the system LLVM, not with Julia’s patched one? That’s not really supported. You get what you get if you don’t use our LLVM. |
@JeffBezanson , @Keno , @StefanKarpinski : rc2 fixed this bug (only Win 10 tested so far). |
@StefanKarpinski That failure comes from Debian's llvm-6.0 . I guess it misses this patch. |
trying to fix Garbage Collect segfault, maybe related to JuliaLang/julia#27952
The text was updated successfully, but these errors were encountered: