# Pluto "Process Exited" due to segmentation fault on macos

**URL:** <https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558>\
**Category:** General Usage\
**Tags:** pluto\
**Created:** [January 13, 2022, 3:25pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558 "2022-01-13T15:25:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![iskyd](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/iskyd/32/44797_2.png) [@iskyd](https://discourse.julialang.org/u/iskyd)\
**Post date:** [January 13, 2022, 3:25pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558/1 "2022-01-13T15:25:02Z")

</div>

Everytime I restart the same notebook I got “Process Exited - Restart”.  
In the log I found

> From worker 2: signal (11): Segmentation fault: 11  
> …  
> Worker 2 terminated.
> 
> **Unhandled Task ERROR:** EOFError: read end of file

This seems to happens on cells where I plot something (using plot jl and stats plots).  
I have to comment all the cells, kill pluto and julia, start julia again, execute Pluto.run() and then execute the cells one by one to make it works.

But this make julia unusable on my macos.  
I’m using macOS Monterey on M1 Chip and 1.7.1

---

<div class="post-metadata">

**Author:** ![goedman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goedman/32/217_2.png) [@goedman](https://discourse.julialang.org/u/goedman)\
**Post date:** [January 13, 2022, 8:32pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558/2 "2022-01-13T20:32:45Z")

</div>

You’re probably hitting similar problems as I reported last November ( [https://github.com/fonsp/Pluto.jl/discussions/1686](https://github.com/fonsp/Pluto.jl/discussions/1686) ).

I now only use it with JULIA\_NUM\_THREADS\<=4 and occasionally it wants a restart, typically less and less after a few restarts. Not ideal, but for now I can live with it. Still, running such a notebook in the REPL always works, so it is likely a Pluto issue.

---

<div class="post-metadata">

**Author:** ![iskyd](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/iskyd/32/44797_2.png) [@iskyd](https://discourse.julialang.org/u/iskyd)\
**Post date:** [January 14, 2022, 5:01pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558/3 "2022-01-14T17:01:43Z")

</div>

Thank you so much!  
Tried with JULIA\_NUM\_THREADS=4 but it didn’t work. Then tried with JULIA\_NUM\_THREADS=3 and seems to work.

---

<div class="post-metadata">

**Author:** ![goedman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goedman/32/217_2.png) [@goedman](https://discourse.julialang.org/u/goedman)\
**Post date:** [January 15, 2022, 2:23pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558/4 "2022-01-15T14:23:16Z")

</div>

Have you also found that the notebooks always seem fine in the REPL?

---

<div class="post-metadata">

**Author:** ![iskyd](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/iskyd/32/44797_2.png) [@iskyd](https://discourse.julialang.org/u/iskyd)\
**Post date:** [January 15, 2022, 6:03pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558/5 "2022-01-15T18:03:27Z")

</div>

Yes, with REPL it seems working fine.  
I noticed that by default Threads.nthreads() return 1. I didn’t expect that.

---

<div class="post-metadata">

**Author:** ![Xavier\_Gonzalez](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xavier_gonzalez/32/36033_2.png) [@Xavier\_Gonzalez](https://discourse.julialang.org/u/Xavier_Gonzalez)\
**Post date:** [May 16, 2022, 11:37pm UTC](https://discourse.julialang.org/t/pluto-process-exited-due-to-segmentation-fault-on-macos/74558/6 "2022-05-16T23:37:19Z")

</div>

I’m having the same problem!!!

This bug is extremely annoying, even with the super helpful workaround. Could someone from Julia please fix this?