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
{{ message }}
Repository navigation
Segmentation fault in IJulia when loading PyCall #1108
This issue only happens in IJulia/Jupyter, not in the julia-terminal.
Minimal reproducer:
[1] using PyCall --> segmentation fault
[1] using PyCall; GC.gc() --> no segmentation fault
Stack trace
in expression starting at none:1
unknown function (ip: 0x78d606b873da) at /usr/lib/x86_64-linux-gnu/libpython3.12.so.1.0
unknown function (ip: 0x78d606b87d5b) at /usr/lib/x86_64-linux-gnu/libpython3.12.so.1.0
pydecref_ at /home/user/.julia/packages/PyCall/1gn3u/src/PyCall.jl:118 [inlined]
pydecref at /home/user/.julia/packages/PyCall/1gn3u/src/PyCall.jl:123
jfptr_pydecref_7752 at /home/user/.julia/compiled/v1.13/PyCall/GkzkC_OwfuA.so (unknown line)
run_finalizer at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gc-common.c:180
jl_gc_run_finalizers_in_list at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gc-common.c:270
run_finalizers at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gc-common.c:316
jl_mutex_unlock at /cache/build/builder-amdci4-4/julialang/julia-ci/src/julia_locks.h:90 [inlined]
jl_type_infer at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gf.c:502
jl_compile_method_internal at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gf.c:3715
ijl_compile_method_instance at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gf.c:4086
ijl_compile_hint at /cache/build/builder-amdci4-4/julialang/julia-ci/src/gf.c:4110
There are enough duplicated issues open I'll just close this for now. Feel free to try/comment on the PR. The plan is to fix CI and merge the fix next week and hopefully tag a release soon after.
Activity
yuyichao commentedon Oct 16, 2026
Yeah most likely #1096. Hopefully will be fixed soon. Ref #1097
yuyichao commentedon Oct 16, 2026
There are enough duplicated issues open I'll just close this for now. Feel free to try/comment on the PR. The plan is to fix CI and merge the fix next week and hopefully tag a release soon after.