# Floop threading and Juliacall produce segmentation fault

**URL:** <https://discourse.julialang.org/t/floop-threading-and-juliacall-produce-segmentation-fault/100717>\
**Category:** General Usage\
**Tags:** question, parallel, python, juliacall\
**Created:** [June 22, 2023, 9:50pm UTC](https://discourse.julialang.org/t/floop-threading-and-juliacall-produce-segmentation-fault/100717 "2023-06-22T21:50:24Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![vchuravy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vchuravy/32/8_2.png) [@vchuravy](https://discourse.julialang.org/u/vchuravy)\
**Post date:** [June 23, 2023, 10:48pm UTC](https://discourse.julialang.org/t/floop-threading-and-juliacall-produce-segmentation-fault/100717/11 "2023-06-23T22:48:18Z")

</div>

Does Python replace/override the fault handlers of Julia?

When multi-threaded GC uses read-protected pages to implement safepoints (e.g. to ask other threads to stop doing work). This causes a benign segmentation fault, but it must be handled by the Julia segmentation handler.

---

_[View the full topic](https://discourse.julialang.org/t/floop-threading-and-juliacall-produce-segmentation-fault/100717)._