Segmentation fault while opening files with cfgrib
See original GitHub issueI am not able to open grib file with cfgrib . I am running into a segmentation fault.
I have tested both:
xarray.open_dataset('test.grib2', engine='cfgrib')
cfgrib.open_datasets('test.grib2')
When I am using pygrib, all works fine. So I assume a problem with cfgrib.
Versions:
In [10]: cfgrib.__version__
Out[10]: '0.9.10.2'
In [11]: xarray.__version__
Out[11]: '2022.9.0'
In [12]: #xarray.__version__
In [13]: import eccodes
In [14]: eccodes.__version__
Out[14]: '2.27.0'
Issue Analytics
- State:
- Created a year ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Segmentation fault when reading example GRIB file ... - GitHub
When running the following example case from https://github.com/ecmwf/cfgrib, my iPython session crashes when using encodes version 2.18.0.
Read more >Segmentation fault after updating eccodes for python
segmentation fault. I noticed that the problem does not occure when running eccodes version 2.17.0 instead of version 2.23.0 or another ...
Read more >1856959 – NCL error while trying to read GRIB2 files
Description of problem: An error occurs while trying to read the contents of a GRIB2-formatted file, either with ncl (via script) or ...
Read more >History of Changes - ECMWF Confluence Wiki
Please use cfgrib and pdbufr instead. ... error on GRIB edition 1 with raw packing; [ECC-1076] - Segmentation fault when reading grib1 file ......
Read more >Package List — Spack 0.20.0.dev0 documentation
It is automatically generated based on the packages in this Spack version. ... code errors that cause segmentation faults or other signals can...
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 FreeTop 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
Top GitHub Comments
Dear Daniel,
does using
python:3.9-slim-bullseye
make any difference? It will give you a more recent version of Python 3.9, and a newer OS baseline image (Debian 11 Bullseye instead of Debian 10 Buster).With kind regards, Andreas.
Interesting. For me, cfgrib 0.9.10.2 works fine with the data. My only difference from you is that my test environment has eccodes 2.26.0 rather than 2.27.0, otherwise the versions are the same as your original failing one.