I’ve been using the debugger with some success in VSCode, but today it was incredibly slow. Like 30 seconds to 2 minutes to step from one line to the next, even when the lines in question didn’t seem to be doing much, e.g., computing a set difference with 2 arrays of under 10 symbols each.
I had set a breakpoint in the code and then did
@run from the REPL.
The highlighted line usually advanced pretty promptly, but the progress indicator in the explorer view kept spinning, and the new data created by the line did not display until the end of the waiting period.
During this time one CPU was at the max running julia. There were also times when VSCode showed high CPU use.
The most obvious difference between this and earlier sessions is that some of the local variables were very large
DataFrames (~ 38k x 100). I never opened up the browser on them, but if the code was trying to precompute what they would look like if I did, that might explain the delay. Although wouldn’t the display show the usual truncated view in any case?
Another possibility is that my use of
ProfileView (I think, definitely some package) is causing trouble. It comes with warning that using GTK on Windows may slow things down by a lot, even 100 fold. I have a
using directive for it, but never ran it during the session. And this is no change from earlier.
It also seemed to me that revise was not picking up my changes; I did a lot of stopping and restarting the REPL. However, a significant number of my changes where type changes, which I don’t think it can handle.
After many minutes of stepping through a program I got a notice that the extension had crashed. This was the only time it crashed in a handful of sessions using it. It was the longest session.
VSCode says I have the Julia 1.0.8 extension; VSCode is 1.50.0; Julia is 1.5.1.
Running on 64 bit Win 10 Enterprise Version 1809 Build 17763