Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pluto crashes on closing #3036

Closed
donovaly opened this issue Sep 29, 2024 · 4 comments
Closed

Pluto crashes on closing #3036

donovaly opened this issue Sep 29, 2024 · 4 comments

Comments

@donovaly
Copy link

In Julia's REPL I started Pluto, and there I read:

Info: │ Press Ctrl+C in this terminal to stop Pluto

But when I do this, I get this error

fatal: error thrown and no exception handler available.
InterruptException()
_jl_mutex_unlock at C:/workdir/src\threading.c:949
jl_mutex_unlock at C:/workdir/src\julia_locks.h:80 [inlined]
ijl_task_get_next at C:/workdir/src\scheduler.c:526
poptask at .\task.jl:1012
wait at .\task.jl:1021
task_done_hook at .\task.jl:694
jfptr_task_done_hook_67126.1 at J:\Julia-1.11\lib\julia\sys.dll (unknown line)
jl_apply at C:/workdir/src\julia.h:2157 [inlined]
jl_finish_task at C:/workdir/src\task.c:319
start_task at C:/workdir/src\task.c:1213

This is strange as I am on Windows. There is no such directory C:/workdir and it can also not be created as one would need admin permissions to do so. So also the error message is wrong.

I use Julia 1.11RC4 under Windows 10 RC4.

I tried to close Pluto also directly after I started, so no notebook was ever loaded or run but the bug persists.

@fonsp
Copy link
Owner

fonsp commented Oct 1, 2024

Hey Uwe! Did Pluto exit? What happens when you press Ctrl+C again?

Ctrl+C is a bit difficult to handle Julia, but it is being worked on (eg JuliaLang/julia#25790).

For the C:/workdir issue, you could make an issue in https://github.com/JuliaLang/julia/issues

@donovaly
Copy link
Author

donovaly commented Oct 1, 2024

Did Pluto exit?

I don't know. The browser tab (Firefox) is still open and does not accept inputs. So the server was shut down but it can be because of the crash.

What happens when you press Ctrl+C again?

Julia outputs just:
^C

For the C:/workdir issue, you could make an issue in https://github.com/JuliaLang/julia/issues

Done: JuliaLang/julia#55957
It seems the problem is that I use the JULIA_DEPOT_PATH environment variable.

@fonsp
Copy link
Owner

fonsp commented Nov 13, 2024

Maybe you could record a video the next time this happens! I'm not sure we can improve this without a video.

@donovaly
Copy link
Author

Maybe you could record a video the next time this happens! I'm not sure we can improve this without a video.

Here you are:
julia_uOxdRe2MdP

This is with Julia 1.11.1 and I performed an update, gc and instantiate before I started Pluto. Now the crash is gone. Only this message in the REPL sounds weird:

fatal: error thrown and no exception handler available.
InterruptException()

because there is no fatal error as Pluto is shut don the normal way.

For reference here the full REPL output:

julia> Pluto.run()
[ Info: Loading...
┌ Info:
└ Opening http://localhost:1234/?secret=IQNZaohK in your default browser... ~ have fun!
┌ Info:
│ Press Ctrl+C in this terminal to stop Pluto
└
fatal: error thrown and no exception handler available.
InterruptException()


┌ Info:
│ Closing Pluto... Restart Julia for a fresh session.
│
│ Have a nice day! 🎈
└
_jl_mutex_unlock at C:/workdir/src\threading.c:949
jl_mutex_unlock at C:/workdir/src\julia_locks.h:80 [inlined]
ijl_task_get_next at C:/workdir/src\scheduler.c:526
poptask at .\task.jl:1012
wait at .\task.jl:1021
task_done_hook at .\task.jl:694
jfptr_task_done_hook_67171.1 at J:\Julia-1.11\lib\julia\sys.dll (unknown line)
jl_apply at C:/workdir/src\julia.h:2157 [inlined]
jl_finish_task at C:/workdir/src\task.c:319
start_task at C:/workdir/src\task.c:1213

julia>

Despite the misleading message about a fatal error, I would say the issue is resolved.

@fonsp fonsp closed this as not planned Won't fix, can't repro, duplicate, stale Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants