Hey everyone. Back here asking for help again
I’m using Gradient notebooks and seeing a peculiar issue. After running a notebook that has some plotting elements, maybe a matplotlib graph, maybe the output of
show_batch(), I am unable to save the notebook. I can keep executing other notebook cells and active terminals continue to operate fine but the Jupyter UI itself become non-responsive. Autosave/checkpointing also stops working.
I’ve been monitoring disk performance using
iostat and cpu using
htop, there isn’t any high resource utilisation or anything weird. For instance, running
02_production.ipynb from the
fastbook repo works fine until the cell with
dls.valid.show_batch(max_n=4, nrows=1). Up until this point, I can keep saving the notebook. After this runs,
Ctrl+S does nothing. If I reload the Jupyter file explorer, it doesn’t respond. The only way to recover is to clear all cookies from my browser (or login from another browser) and reload Jupyter. Obviously, this also wipes out all unsaved changes from the notebooks.
I’m tearing my hair out over this. Been trying to troubleshoot this for over a month to no avail. Paperspace support has also been unable to help. You’re my last resort guys.
Edit: actually I’m not even sure what the trigger is. E.g. after simply running the first cell in this notebook, which is just imports, the whole thing gets stuck.
I can keep on running the other cells in the notebook, any terminals opened separately continue to work just fine. It’s only Jupyter specific stuff like navigating through directories, saving notebooks, etc. that get stuck. Issue seems to be in both JupyterLab and Classic Notebook interfaces.