-
Notifications
You must be signed in to change notification settings - Fork 289
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 running some code #9283
Comments
@rchiodo It seems not the problem of matplotlib, today I encouter Error 3228369022 again when using numpy matrix multiplication @, below code will produces the error; import numpy as np
a = np.array([[1., 0., 0.],
[0., 1., 0.],
[0., 0., 1.]])
print(a@a) |
What do you have for this setting here:
It looks to me like that code is crashing, not the specific code you ran. Otherwise, you'd have this in your log:
|
That looks like you're not using that setting so my guess was wrong. The other thing that happens is we request the kernel information from the kernel as well. Not sure how that would cause a crash. Can you ever run a kernel? Or do all kernels crash immediately? |
My suspicion now is that something running in the kernel on startup fails and eventually causes it to crash. We might be able to get more information by running this:
That should start the kernel the same way we are. |
@rchiodo Usually I can successfully start the jupyter kernel and execute the code, just only in a few cases (such as the above two) will the jupyter kernel die. For example, I execute the following code: import numpy as np
a = np.array([[1., 0., 0.],
[0., 1., 0.],
[0., 0., 1.]]) The kernel will not die, its log is
|
Hmm. Very weird that that other code crashes the kernel. The only difference being the print statement. You might try running this first:
That gets the kernel to log to a file called 'mylog.log'. The only other thing I can think of is to debug the kernel itself. It'd probably be easier to just upgrade your python environment though. |
Yes, this is a rare issue, if I switch to another python virtual env, there is no problem. I am curious what |
This error code stands for 'external exception' as far as I know. This generally means some part of the app called into another dll that caused a crash/exit. Without debugging the call that caused the problem, it's really hard to tell why. |
Closing so that we can handle this better and provide a more contextual error message, see here #9375 |
Environment data
Expected behaviour
Expect the matplotlib can show the image
Actual behaviour
The kernel died
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for
Jupyter
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toJupyter
)The text was updated successfully, but these errors were encountered: