-
Notifications
You must be signed in to change notification settings - Fork 0
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
Segmentation fault error in tests #65
Comments
Check https://docs.xarray.dev/en/stable/whats-new.html for issues related to segmentation fault. Also check pydata/xarray#4100. About using |
parallel
in xarray.open_mfdataset
By switching to the h5netcdf engine this issue can probably be avoided |
Also, if it only happens during the loading step, moving to Zarr instead of netCDF would help as well. Although that would require a bit of an overhaul of the code... |
also, check this GA action that is failed on macos latest due segfault error. |
Yeah this is quite clear. It's using thread based concurrency, and the netCDF4 backend is not thread-safe :/ The problem with this is that it will not always cause errors, but only when certain conditions align, e.g. two netCDF4 processes trying to access the same (part) of the file at the same time. |
This is related to #62.
We found out using
parallel=True
inxarray.open_mfdataset
infapar_lai.py
returns segmentation fault errors on linux and macos, see GA action ubuntu and mac.Example log of GA action on linux
The text was updated successfully, but these errors were encountered: