Kernel died with exit code 1073741845.
See original GitHub issueHi,
When I tried to launch interactive window in vscode, it failed with the error below. Could you please help to identify what’s wrong with it?
thanks, alex
Issue Type: Bug
Kernel died with exit code 1073741845. C:\Users\Alex.wang.virtualenvs\vtree-_4DfoHDc\lib\site-packages\traitlets\traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use ‘hmac-sha256’ instead of ‘“hmac-sha256”’ – or use CUnicode. warn( C:\Users\Alex.wang.virtualenvs\vtree-_4DfoHDc\lib\site-packages\traitlets\traitlets.py:2151: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use ‘5995421f-97b9-4627-9c28-0b10e2db4c56’ instead of ‘b"5995421f-97b9-4627-9c28-0b10e2db4c56"’. warn( Bad address (C:\projects\libzmq\src\epoll.cpp:100)
Extension version: 2021.6.832593372 VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:13:13.157Z) OS version: Windows_NT x64 10.0.19042
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i5-10210U CPU @ 1.60GHz (8 x 2112) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 7.84GB (0.52GB free) |
Process Argv | |
Screen Reader | no |
VM | 0% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30267464
pythonptprofiler:30281270
vshan820:30294714
pythondataviewer:30285071
vscus158:30286553
vscgsv2:30301612
vscorehov:30302759
bridgeflightcf:30302070
vscod805:30301674
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (4 by maintainers)
Top GitHub Comments
I solved this issue by reinstall Pyzmq==19.0.2.
I resolved my issue using your method as well, though in my case I was still prompted that the dependency conflict of parso and jedi exist. Hope this entire issue can be better handled in later releases.