)
at 0x0006871e (/home/user/project/dso/julia/lib/julia/libjulia-internal.so.1.10) in /cache/build/builder-amdci4-6/julialang/julia-release-1-dot-10/src/init.c:336
#10 0x00007f06170a65c3 in execute_native_thread_routine () at 0x000e05c3 (/lib/libstdc++.so.6) in /lib/libstdc++.so.6
#11 0x00007f0616d66084 in start_thread () at 0x0008b084 (/lib/libc.so.6) in /lib/libc.so.6
#12 0x00007f0616de860c in clone3 () at 0x0010d60c (/lib/libc.so.6) in /lib/libc.so.6
```
---
### Author:  [@Liozou](https://discourse.julialang.org/u/Liozou)
#### Post date: [January 12, 2024, 5:12pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/4 "2024-01-12T17:12:36Z")
I’m afraid solving the root issue is beyond my level of expertise. But if you do not do any kind of IO from the julia side, then I guess you should not care about libuv. In that case, I would suggest creating your own `jl_atexit_hook_nolibuv` function consisting of the [definition of `jl_atexit_hook`](https://github.com/JuliaLang/julia/blob/5b6a94da5af35a4aa91759cac2f8db7669a6ec2a/src/init.c#L240-L356) with all the parts related to libuv removed. It looks like except these `uv_` calls, all the other ones are `jl_` function calls, which should be exported so accessible from within your code.
Or you could completely drop the call to `jl_atexit_hook`. That’s far from ideal if julia has stuff remaining to be done at this point, but otherwise I would assme that’s fine to do if your program exits immediately after anyway?
---
### Author:  [@xapkohheh](https://discourse.julialang.org/u/xapkohheh)
#### Post date: [January 12, 2024, 6:15pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/5 "2024-01-12T18:15:17Z")
not calling `jl_atexit_hook` at all causes a different segfault by jealloc when thread is being destroyed (i use julia in a dedicated thread)
I’ll try to make an atexit variant that does not make any uv\_ calls and see.
as a workaround to avoid crashes - i can just to `std::quick_exit` , but since it’s done in software’s exit hooks - i rob other plugins from being able to run exit callbacks.
---
### Author:  [@xapkohheh](https://discourse.julialang.org/u/xapkohheh)
#### Post date: [January 12, 2024, 7:29pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/6 "2024-01-12T19:29:21Z")
hm… it seems that there is just too much of what is used in original `jl_atexit_hook` is not exported, so i cannot just make my own version of it…
---
### Author:  [@mkitti](https://discourse.julialang.org/u/mkitti)
#### Post date: [January 12, 2024, 7:37pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/7 "2024-01-12T19:37:47Z")
What packages are you using? Do any of them install an at exit hook?
---
### Author:  [@xapkohheh](https://discourse.julialang.org/u/xapkohheh)
#### Post date: [January 12, 2024, 7:43pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/8 "2024-01-12T19:43:55Z")
no packages, clean new julia
and for this test all i do is
```julia
jl_init();
jl_atexit_hook(0);
```
(but in a dedicated thread)
all julia functional otherwise seem to be working fine, can run some evaluations, gc works, no problem there, just in the exiting
---
### Author:  [@mkitti](https://discourse.julialang.org/u/mkitti)
#### Post date: [January 12, 2024, 8:55pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/9 "2024-01-12T20:55:02Z")
Does the other software also use libuv?
---
### Author:  [@xapkohheh](https://discourse.julialang.org/u/xapkohheh)
#### Post date: [January 12, 2024, 9:26pm UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/10 "2024-01-12T21:26:47Z")
i looked through it’s .so files and third party library licenses page - nope, no libuv
---
### Author:  [@paulmelis](https://discourse.julialang.org/u/paulmelis)
#### Post date: [October 19, 2024, 12:32am UTC](https://discourse.julialang.org/t/embedding-julia-jl-atexit-hook-always-segfaults/108722/11 "2024-10-19T00:32:12Z")
> [@xapkohheh](#):
>
> Does anyone have an insight of what is really going on here, or what can I do to determine the cause and find a solution?
Perhaps see this issue, and specifically [this comment](https://github.com/JuliaLang/julia/issues/46298#issuecomment-1220940156) about a simple workaround to test. It worked for me to get rid of an at-exit memory-related error while trying to use Julia through Python in Blender 😉