# What else can cause "UNHANDLED TASK ERROR: EOFError: read end of file"?

**URL:** <https://discourse.julialang.org/t/what-else-can-cause-unhandled-task-error-eoferror-read-end-of-file/102596>\
**Category:** General Usage\
**Tags:** question, distributed\
**Created:** [August 8, 2023, 10:29am UTC](https://discourse.julialang.org/t/what-else-can-cause-unhandled-task-error-eoferror-read-end-of-file/102596 "2023-08-08T10:29:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![schlichtanders](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/schlichtanders/32/32145_2.png) [@schlichtanders](https://discourse.julialang.org/u/schlichtanders)\
**Post date:** [August 8, 2023, 10:29am UTC](https://discourse.julialang.org/t/what-else-can-cause-unhandled-task-error-eoferror-read-end-of-file/102596/1 "2023-08-08T10:29:01Z")

</div>

When using Pluto for long running Pluto notebooks, after some days, I am running into the following

```julia
Worker 6 terminated.
UNHANDLED TASK ERROR: EOFError: read end of file
Stacktrace:
 [1] wait_locked
   @ ./stream.jl:947
 [2] unsafe_read
   @ ./stream.jl:955
 [3] unsafe_read
   @ ./io.jl:761 [inlined]
 [4] unsafe_read
   @ ./io.jl:760
 [5] read!
   @ ./io.jl:762 [inlined]
 [6] deserialize_hdr_raw
   @ /usr/local/julia/share/julia/stdlib/v1.9/Distributed/src/messages.jl:167 [inlined]
 [7] message_handler_loop
   @ /usr/local/julia/share/julia/stdlib/v1.9/Distributed/src/process_messages.jl:172
 [8] process_tcp_streams
   @ /usr/local/julia/share/julia/stdlib/v1.9/Distributed/src/process_messages.jl:133
 [9] #103
   @ ./task.jl:514

```

The best help I could find so far is from this [stackoverflow](https://stackoverflow.com/questions/46515249/meaning-of-julia-error-error-unhandled-task-failure-eoferror-read-end-of-fi) which mentions and out of memory as on potential source of this error.

I indeed was able to fix a couple of memory leaks on my side but think that there is no memory now any longer (I am plotting memory consumption and it looks constant).

**Hence I am looking for other potential sources of this error, but couldn’t find any so far.** (Apparently you get it too if you `interrupt(2)` a worker 2, but this will also output more loggings about which error was not handled - I really only have the above output, nothing more)