Due to a change in the way that the SIMD support flags are initialized in libjpeg-turbo 2.1.5, some applications (e.g., libvips, Chromium) crash with an illegal opcode error (SIGILL) because they call decoding functions in a different thread than that which initialized the library. Example kernel log message accompanying a crash in Chromium: traps: CompositorTileW[11830] trap invalid opcode ip:7f2468e0193e sp:7f241ff55060 error:0 in libjpeg.so.62.3.0[7f2468def000+5f000] Upstream has pushed a patch to fix this issue: https://github.com/libjpeg-turbo/libjpeg-turbo/commit/d743a2c12e889f7605a56f5144ae2e3899c9dd4f.patch It would be good to add this patch as a revbump to the Gentoo ebuild.
Sure. Fancy doing a PR?
Okay, sure. Stand by.
https://github.com/gentoo/gentoo/pull/29473
Thanks!
35 commit 0d7aaed3e9ca8dfda55d24bdb1c6f8d81251873f 36 Author: Matt Whitlock <gentoo@mattwhitlock.name> 37 Date: Tue Feb 7 19:44:18 2023 -0500 38 39 media-libs/libjpeg-turbo: add patch to avoid SIGILL for 2.1.5 40 41 See: https://github.com/libjpeg-turbo/libjpeg-turbo/issues/649 42 Signed-off-by: Matt Whitlock <gentoo@mattwhitlock.name> 43 Closes: https://github.com/gentoo/gentoo/pull/29473 44 Signed-off-by: Sam James <sam@gentoo.org>
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4fd20b57bf481919243b099f0d3179ea38ce23ce commit 4fd20b57bf481919243b099f0d3179ea38ce23ce Author: Sam James <sam@gentoo.org> AuthorDate: 2023-02-09 01:47:32 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-09 01:47:32 +0000 media-libs/libjpeg-turbo: add 2.1.5.1, drop 2.1.5-r1 Closes: https://bugs.gentoo.org/893552 Signed-off-by: Sam James <sam@gentoo.org> media-libs/libjpeg-turbo/Manifest | 2 +- ...-initialize-simd_support-before-every-use.patch | 437 --------------------- ....1.5-r1.ebuild => libjpeg-turbo-2.1.5.1.ebuild} | 4 - 3 files changed, 1 insertion(+), 442 deletions(-)
