Processed: HDF 4.3.1 uploaded to unstable
Antonio Valentino
antonio.valentino at tiscali.it
Mon Oct 20 21:20:49 BST 2025
Dear Bas,
Il 20/10/25 08:20, Sebastiaan Couwenberg ha scritto:
> On 10/20/25 8:03 AM, Antonio Valentino wrote:
>> Finally I manage to spare some time to investigate the issue and I
>> realized that there is a very similar problem on rioxarray.
>> For rioxarray I was able to identify a minimum set of tests (two)
>> that, if run together, can trigger the issue. I reported it in [1].
>>
>> The problem, both for satpy and rioxarray, seems to happen during the
>> garbage collection of objects representing an HDF4 file.
>> In satpy it libhdf4 is used through pyhfd, while in rioxarray through
>> rasterio and gdal.
>>
>> Are you aware of any change in the libhdf4 API of v4.3.x that could
>> lead to this kind of issues?
>
> I don't know more than what upstream documented:
>
> https://github.com/HDFGroup/hdf4/blob/hdf4.3.1/release_notes/
> RELEASE.txt#L47
>
> 4.3.1 did have focus on memory leak fixes.
>
OK, thanks
>> The satpy error apparently happens in a portion of the code that
>> exploits treading.
>> Apart for making the debugging harder, I'm not sure this detail is
>> relevant for the specific problem.
>>
>> If my understanding is correct, the relevant portion of the satpy
>> implementation is being rewritten in the upstream main branch for
>> unrelated reasons. I will give it a try ASAP to understand if the new
>> implementation has the same issues on debian.
>>
>> Unfortunately, I have very few time to dedicate to it in this period.
>> satpy has been removed form testing and rioxarray will be removed very
>> soon.
>> I'm sorry for that and I really hope that it does not creates too many
>> issues.
>
> There is a new satpy release we can see if that resolves anything.
I have satpy v0.58 ready on my laptop.
It is affected by the issue, that is why I have still not uploaded.
But I can push to git if you want.
> I guess your lack of time is also the reason that gmtsar hasn't been
> updated to 6.6 yet.
>
> If you want I can update these packages.
Also for gmtsar I have half of the job done.
Currently there are several build errors but at a very first look it
seems something relatively easy to solve.
Probably linked to an incompatibility with gcc 15.
If you want I can push to salsa.
kind regards
--
Antonio Valentino
More information about the Pkg-grass-devel
mailing list