# Kernel Dies when running CADET **URL:** \ **Category:** CADET Troubleshooting\ **Created:** [October 27, 2022, 2:34pm UTC](https://forum.cadet-web.de/t/kernel-dies-when-running-cadet/590 "2022-10-27T14:34:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![j.schmoelder](https://forum.cadet-web.de/user_avatar/forum.cadet-web.de/j.schmoelder/32/93_2.png) [@j.schmoelder](https://forum.cadet-web.de/u/j.schmoelder)\ **Post date:** [October 27, 2022, 2:34pm UTC](https://forum.cadet-web.de/t/kernel-dies-when-running-cadet/590/1 "2022-10-27T14:34:44Z")
There is currently an issue which leads to a crash of the Python Kernel when running CADET on Windows. After some digging, we found out that the issue comes with one of our dependencies, namely hdf5/h5py. When HDF5 v1.12.2 was released, h5py seems to not have properly included the new headers. Which leads to the following error: ```auto Warning! ***HDF5 library version mismatched error*** The HDF5 header files used to compile this application do not match the version used by the HDF5 library to which this application is linked. Data corruption or segmentation faults may occur if the application continues. This can happen when an application was compiled by one version of HDF5 but linked with a different version of static or shared HDF5 library. You should recompile the application or check your shared library related settings such as 'LD_LIBRARY_PATH'. You can, at your own risk, disable this warning by setting the environment variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'. Setting it to 2 or higher will suppress the warning messages totally. Headers are 1.12.2, library is 1.12.1 ``` We know other projects seem to have the same issue and we contacted the h5py developers. > > > In \[TorchGeo\](https://github.com/microsoft/torchgeo), we use h5py to load sample… HDF5 files in our unit tests. These tests are run on CI for Linux/macOS/Python. Since the new 3.7.0 release, our tests have been failing on Windows (for example, \[here\](https://github.com/microsoft/torchgeo/runs/6739917905?check\_suite\_focus=true)). I believe there may be an issue with the h5py 3.7.0 wheels on Windows. I don't have easy access to a Windows machine to test this, but I'm guessing something as simple as importing h5py will fail on Windows, at least with Python 3.10. > > \* Operating System: Microsoft Windows Server 2022 (10.0.20348) > \* Python version: 3.10.4 > \* Source: setup-python GitHub Action > \* h5py version: 3.7.0 > \* HDF5 version: whatever comes with the 3.7.0 Windows wheels > \* The full traceback/stack trace shown: > \`\`\` > Fatal Python error: Aborted > Current thread 0x000013c4 (most recent call first): > File "\", line 241 in \_call\_with\_frames\_removed > File "\", line 1184 in exec\_module > File "\", line 688 in \_load\_unlocked > File "\", line 1006 in \_find\_and\_load\_unlocked > File "\", line 1027 in \_find\_and\_load > File "\", line 241 in \_call\_with\_frames\_removed > File "\", line 1078 in \_handle\_fromlist > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\h5py\\\_\_init\_\_.py", line 56 in \ > File "\", line 241 in \_call\_with\_frames\_removed > File "\", line 883 in exec\_module > File "\", line 688 in \_load\_unlocked > File "\", line 1006 in \_find\_and\_load\_unlocked > File "\", line 1027 in \_find\_and\_load > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\outcomes.py", line 288 in importorskip > File "D:\\a\\torchgeo\\torchgeo\\tests\\datasets\\test\_so2sat.py", line 18 in \ > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\assertion\\rewrite.py", line 168 in exec\_module > File "\", line 688 in \_load\_unlocked > File "\", line 1006 in \_find\_and\_load\_unlocked > File "\", line 1027 in \_find\_and\_load > File "\", line 1050 in \_gcd\_import > File "C:\\Miniconda\\envs\\test\\lib\\importlib\\\_\_init\_\_.py", line 126 in import\_module > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\pathlib.py", line 533 in import\_path > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\python.py", line 608 in \_importtestmodule > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\python.py", line 519 in \_getobj > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\python.py", line 301 in obj > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\python.py", line 536 in \_inject\_setup\_module\_fixture > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\python.py", line 522 in collect > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\runner.py", line 369 in \ > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\runner.py", line 338 in from\_call > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\runner.py", line 369 in pytest\_make\_collect\_report > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_callers.py", line 39 in \_multicall > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_manager.py", line 80 in \_hookexec > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_hooks.py", line 265 in \_\_call\_\_ > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\runner.py", line 537 in collect\_one\_node > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 824 in genitems > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 827 in genitems > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 657 in perform\_collect > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 332 in pytest\_collection > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_callers.py", line 39 in \_multicall > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_manager.py", line 80 in \_hookexec > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_hooks.py", line 265 in \_\_call\_\_ > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 321 in \_main > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 268 in wrap\_session > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\main.py", line 315 in pytest\_cmdline\_main > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_callers.py", line 39 in \_multicall > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_manager.py", line 80 in \_hookexec > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\pluggy\\\_hooks.py", line 265 in \_\_call\_\_ > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\config\\\_\_init\_\_.py", line 164 in main > File "C:\\Miniconda\\envs\\test\\lib\\site-packages\\\_pytest\\config\\\_\_init\_\_.py", line 187 in console\_main > File "C:\\Miniconda\\envs\\test\\Scripts\\pytest.exe\\\_\_main\_\_.py", line 7 in \ > File "C:\\Miniconda\\envs\\test\\lib\\runpy.py", line 86 in \_run\_code > File "C:\\Miniconda\\envs\\test\\lib\\runpy.py", line 196 in \_run\_module\_as\_main > \`\`\` In the meantime, for a quick fix, simply downgrade h5py: ```auto pip uninstall h5py pip install h5py==3.6.0 ``` We’re also working on a new hotfix release of CADET-Python which will put bounds on the h5py version until the issue is resolved upstream. Thanks for understanding! ---
**Author:** ![h.lanzrath](https://forum.cadet-web.de/user_avatar/forum.cadet-web.de/h.lanzrath/32/1186_2.png) [@h.lanzrath](https://forum.cadet-web.de/u/h.lanzrath)\ **Post date:** [January 27, 2026, 7:43am UTC](https://forum.cadet-web.de/t/kernel-dies-when-running-cadet/590/2 "2026-01-27T07:43:01Z")