# Segmentation fault (core dumped) in 1.11.5 REPL

**URL:** <https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323>\
**Category:** General Usage\
**Created:** [April 23, 2025, 9:21am UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323 "2025-04-23T09:21:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xing\_Shi\_Cai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xing_shi_cai/32/14128_2.png) [@Xing\_Shi\_Cai](https://discourse.julialang.org/u/Xing_Shi_Cai)\
**Post date:** [April 23, 2025, 9:21am UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323/1 "2025-04-23T09:21:39Z")

</div>

I was trying to use my own package [Pivot.jl](https://gitlab.com/newptcai/Pivot.jl) in REPL. When I type `m<TAB>`, I got a segmentation fault. I can try to avoid autocompletion. But it’s a bit annoying not able to use it. Does anyone have similar problem and has found a workaround?

```julia
julia> using Pivot

julia> m
[87616] signal 11 (1): Segmentation fault
in expression starting at none:0
_PyInterpreterState_GET at /usr/local/src/conda/python-3.12.6/Include/internal/pycore_pystate.h:133 [inlined]
notify_code_watchers at /usr/local/src/conda/python-3.12.6/Objects/codeobject.c:32 [inlined]
code_dealloc at /usr/local/src/conda/python-3.12.6/Objects/codeobject.c:1703
pydecref_ at /home/xing/.julia/packages/PyCall/1gn3u/src/PyCall.jl:118
pydecref at /home/xing/.julia/packages/PyCall/1gn3u/src/PyCall.jl:123
jfptr_pydecref_4550 at /home/xing/.julia/compiled/v1.11/PyCall/GkzkC_ZLpbM.so (unknown line)
run_finalizer at /cache/build/tester-amdci5-12/julialang/julia-release-1-dot-11/src/gc.c:303
jl_gc_run_finalizers_in_list at /cache/build/tester-amdci5-12/julialang/julia-release-1-dot-11/src/gc.c:393
run_finalizers at /cache/build/tester-amdci5-12/julialang/julia-release-1-dot-11/src/gc.c:439
enable_finalizers at ./gcutils.jl:161 [inlined]
unlock at ./lock.jl:178 [inlined]
macro expansion at ./lock.jl:275 [inlined]
#282 at /cache/build/tester-amdci5-12/julialang/julia-release-1-dot-11/usr/share/julia/stdlib/v1.11/REPL/src/LineEdit.jl:2851
jfptr_YY.282_8768.1 at /home/xing/.julia/juliaup/julia-1.11.5+0.x64.linux.gnu/share/julia/compiled/v1.11/REPL/u0gqU_4x0TT.so (unknown line)
jl_apply at /cache/build/tester-amdci5-12/julialang/julia-release-1-dot-11/src/julia.h:2157 [inlined]
start_task at /cache/build/tester-amdci5-12/julialang/julia-release-1-dot-11/src/task.c:1202
Allocations: 7632460 (Pool: 7632168; Big: 292); GC: 13
Segmentation fault (core dumped)

```

---

<div class="post-metadata">

**Author:** ![mzaffalon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mzaffalon/32/214168_2.png) [@mzaffalon](https://discourse.julialang.org/u/mzaffalon)\
**Post date:** [April 23, 2025, 9:36am UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323/2 "2025-04-23T09:36:03Z")

</div>

It looks related to `SymPy/PyCall`. Does the tab completion work with `using SymPy`only?

---

<div class="post-metadata">

**Author:** ![Benny](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Benny](https://discourse.julialang.org/u/Benny)\
**Post date:** [April 23, 2025, 10:07am UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323/3 "2025-04-23T10:07:26Z")

</div>

Possibly related: [Segmentation Fault · Issue #1090 · JuliaPy/PyCall.jl](https://github.com/JuliaPy/PyCall.jl/issues/1090)

---

<div class="post-metadata">

**Author:** ![mzaffalon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mzaffalon/32/214168_2.png) [@mzaffalon](https://discourse.julialang.org/u/mzaffalon)\
**Post date:** [April 23, 2025, 10:33am UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323/4 "2025-04-23T10:33:51Z")

</div>

See also [Tab Completion Freezing for Python Function Arguments · Issue #1085 · JuliaPy/PyCall.jl · GitHub](https://github.com/JuliaPy/PyCall.jl/issues/1085)

---

<div class="post-metadata">

**Author:** ![ianshmean](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ianshmean/32/216042_2.png) [@ianshmean](https://discourse.julialang.org/u/ianshmean)\
**Post date:** [April 23, 2025, 1:14pm UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323/5 "2025-04-23T13:14:32Z")

</div>

Regarding a workaround add this to your startup.jl to disable tab completion hinting.

```julia
if VERSION >= v"1.11.0-0"
  atreplinit() do repl
      repl.options.hint_tab_completes = false
  end
end

```

Once you’ve done that can you check if you get the same segfault just doing

```julia
julia> using Pivot

julia> m<tab>

```

---

<div class="post-metadata">

**Author:** ![Xing\_Shi\_Cai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xing_shi_cai/32/14128_2.png) [@Xing\_Shi\_Cai](https://discourse.julialang.org/u/Xing_Shi_Cai)\
**Post date:** [April 24, 2025, 2:15am UTC](https://discourse.julialang.org/t/segmentation-fault-core-dumped-in-1-11-5-repl/128323/6 "2025-04-24T02:15:45Z")

</div>

It seems to be a bit random. This morning I cannot trigger this any more.