Closed mattcbro closed 2 years ago
Hi @mattcbro,
I don't have time to look into this right now. Maybe next week.
I'm guessing this has something to do with either Gtk.jl or one of Plots.jl's dependencies - simply because I doubt InspectDR itself does much to cause side effects regarding threads - especially if all you do is load up the code (not actually using the plot yet).
That being said, I am kind of interested in eventually adding threading support to InspectDR, so investigating this bug might help me at least get familiar with the basic threading API.
It's definitely real. I got bit by it again running a simulation. It was taking an eternity to run and then I remembered I was using inspectdr(). Had to kill the process and restart it. After that it ran in about 5 seconds.
I'm pretty busy myself right now so I understand the delay. Whenever you get a chance to look at this is fine by me. The interaction is quite strange. Of course the julia people are saying it's inspectdr's fault LOL.
Oh there is this bug in Gtk that was cited as well, so you may be right about the Gtk thing. https://github.com/JuliaGraphics/Gtk.jl/issues/503
The linked bug in Gtk was closed. Shouldn't this issue be also closed as resolved in Gtk then?
Agreed. Most likely was a Gtk bug. I completely forgot about this issue.
Someone can re-open if this is still a problem.
Initializing with the inspectdr() command causes threaded code to run up to 7000 times slower. Here is the test code from issue https://github.com/JuliaLang/julia/issues/40535