Kernel not restarting sometimes
See original GitHub issueimport tensorflow is one way to reproduce: clip. Further, 4.1.4 prints INFO-level messages (also shown), which didn’t occur in 4.1.3, now needing manually setting os.environ['TF_CPP_MIN_LOG_LEVEL'] = '1' to disable.
It also doesn’t always reproduce; still unsure how it works exactly.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:23 (12 by maintainers)
Top Results From Across the Web
Restarting the Jupyter kernel sometimes does not work
The only workaround I have found is to restart DataSpell. Thank you!
Read more >If your Mac restarts and a message appears - Apple Support
If the faulty software is not identified and your Mac continues to experience kernel panics, try the following: Restart your Mac in safe...
Read more >Jupyter notebook kernel constantly needs to be restarted
Restarting the kernel is the only solution I've been able to find and that makes development painfully slow. I'm running these versions for ......
Read more >Mac keeps restarting: how to fix a kernel panic - Setapp
It's not only an outdated system that might cause kernel panic, old and incompatible software is another common issue. The best practice is...
Read more >How to troubleshoot kernel crashes, hangs, or reboots with ...
... developers who need to reboot a machine often for testing purposes. Using kexec for rebooting into a normal kernel is simple, but...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Fixed by https://github.com/spyder-ide/spyder/pull/19411
If the frontend receives an error while restarting, it will abort. But if the kernel sends an error while closing, then the frontend aborts, even though the new kernel is fine.
@ccordoba12 Found a different way to reproduce: importing a compiled
.cmodule (.pyd) and calling its method.C code
setup.py
Run
python setup.py build, then drag the proper.pydout ofbuildso that it’s visible to Python, then in separate.py, runTensorFlow does import from
.pyd, so this might explain the problem (though, wasn’t it working for older TFs? They also import.pyd, but above script actually errors, so maybe it reacts to errors - dunno).