libjxl 0.6.1 has an assertion failure in LowMemoryRenderPipeline::Init() in render_pipeline/low_memory_render_pipeline.cc.
Looks like this is the patch:
So I guess we need another prerelease snapshot. The reporter's crash log has this, which *seemingly* indicates bad instructions were being run somehow, though I don't understand how that's possible via an assertion:
 888096 illegal hardware instruction ./decode_oneshot /tmp/poc /dev/null /dev/null
Maintainer, please bump.
libjxl is at v0.7rc now but there are some fixes in v0.7.x afterwards.
I am not sure now if to bump to the release candidate or it is better to wait till 0.7.0 is finished.
The bug has been referenced in the following commit(s):
Author: Daniel Novomesky <email@example.com>
AuthorDate: 2022-09-02 19:43:46 +0000
Commit: Andreas Sturmlechner <firstname.lastname@example.org>
CommitDate: 2022-09-14 18:12:48 +0000
media-libs/libjxl: version bump to 20220825 snapshot
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Daniel Novomesky <email@example.com>
Signed-off-by: Andreas Sturmlechner <firstname.lastname@example.org>
media-libs/libjxl/Manifest | 1 +
media-libs/libjxl/libjxl-0.7.0_pre20220825.ebuild | 74 +++++++++++++++++++++++
2 files changed, 75 insertions(+)
Thanks! Please stabilize when ready