-
Notifications
You must be signed in to change notification settings - Fork 10
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
Segfault when exiting a Julia v1.11.1 session with multiple threads #45
Comments
I'm seeing the same problem with Julia 1.11.0 upon exit after plotting. Same errors as above but with the python path /usr/local/src/conda/python-3.11.0 |
Well, I'm only familiar with using the package manager to install registered packages so I'd have to do a bit of research on how to point it at a fork on github version instead (and how to unpick the changes when I want to revert). I'll have a go but can't promise how soon |
You can easily install from that PR's GitHub branch into a temporary environment with the following command: julia -e '
using Pkg
Pkg.activate(; temp=true)
Pkg.add(PackageSpec(url="https://github.com/sethaxen/PythonPlot.jl", rev="fixsegfault"))
using PythonPlot' Note that the following should reproduce the segfault: julia -e '
using Pkg
Pkg.activate(; temp=true)
Pkg.add("PythonPlot")
using PythonPlot' |
Thanks, but in my case I've been using pythonplot as a backend for Plots.jl. To test that do I have to make my own fork of Plots.jl and rebuild it to use a local clone of PythonPlot or would it detect the local version by default? |
If I launch a Julia v1.11.1 session with more than 1 thread and if PythonPlot at any point enters scope, then Julia segfaults when I call
exit
. Besides just being annoying, this seems to prevent dependents of PythonPlot from being registered, since the General registry's automated tests seem to use multiple threads. This does not happen on Julia v1.10.6.After cloning the master branch to my machine and instantiating it, I execute the following commands:
Here's my environment info
The text was updated successfully, but these errors were encountered: