-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Kernel dies when trying to run PyTorch code on Linux #5060
Comments
@ccordoba12 Does mixing Spyder versions from PyPi and conda might have some responsibility here? According to the package dump posted by the user, Spyder 3.1.4 and 3.2.1 are both listed:
|
Probably, but did you try to run the OP code? |
Thank you very much for your answering. also i run this code with the same version in my other computer.it works well!!! I try to solve the mixing version problem. delete the redundant package 3.1.4.but still "kernel died,restarting" first I doubt whether Spyder and pytorch have collision in the kernel. |
It seems this is fixed in the latest version of PyTorch: |
not only it has errors in the spyder,but also in jupyter and terminal.. |
Just now,I update all the packages in anaconda
delightedly the code runs well in terminal and jupyter,but the error in the spyder also exists |
Well, I'm running the latest package versions on my current setup, and it works as expected. Any ideas @ccordoba12 ? |
Also, the user reports that on a new installation, the package works. @selous123 Have you tried to create a new conda environment on your conflicting PC? |
everything goes well when i use Source installation instead of "pip install..." as official website proposal to reinstall my pytorch and it works. thank you very much |
@selous123 For future installations, PyTorch developers recommend to install the package using conda:
I'm glad that it works as expected |
Please see this SO question for the details:
https://stackoverflow.com/questions/45875837/spyder-just-kernel-died-restarting-when-i-run-net-forward-in-pytorch
@andfoy, please take a look at this one.
The text was updated successfully, but these errors were encountered: