-
Notifications
You must be signed in to change notification settings - Fork 294
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
Remote Jupyter connection with long running command: Extension host terminated due to memory #3324
Comments
The output from developer tools console:
|
@simplelife2010 do you have a possible repro case? If not, was the long running cell outputting anything? It's hard to tell what caused the extension host to run out of memory. We could probably fix the reattach, but we'd need more info to figure out what's causing the memory problem. |
@rchiodo Yes, I have. It's not precisely my initial setup (which would require specific training data to reproduce), but I found a simpler setup using code from an official Tensorflow tutorial. The console output is a little different so I will attach it again. The extension host terminates after about 10 minutes. This is the code I run on the remote Jupyter host (an AWS EC2 instance):
|
This is the IPython output:
|
This is the console output:
|
Thanks that helps a lot. |
Hey @simplelife2010. I had actually just fixed an issue that looks like it might be similar to yours. The other issue is here: In my last post in that thread I provided a link to our development build, which should have the fix at this point if you want to try it out. |
This error might be different than the other bug. I'm getting a perf issue. |
We have this exact same issue - seems not to be solved as of today... |
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version vscode-python#3977): TrueExpected behaviour
When connecting to a remote Jupyter server, I expect the VS Code extension host not to terminate unexpectedly, even when I run long running commands remotely (> 50 minutes), for example training machine learning models using Tensorflow.
Actual behaviour
When connecting to a remote Jupyter server and executing long running (> 50 minutes) commands like model.fit(), after approx. 50 minutes I receive a popup 'Extension host terminated unexpectedly' with the option to restart the extension host. The connection to the Jupyter session is lost and I receive no further output from the long running command, even if I restart the extension host. I cannot reconnect to the kernel which seems to be still running (as I can see on the server). I also cannot interrupt or restart this kernel, as the corresponding buttons show no reaction. To continue working I have to kill the running kernel on the Jupyter server. When I have done this and try to start another Jupyter session from VS Code, I receive the message 'Cannot execute code, session has been disposed.'
Steps to reproduce:
Logs
No output in the output panel
The text was updated successfully, but these errors were encountered: