Source: firefox
Version: 138.0.1-1
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64
X-Debbugs-Cc: debian-powe...@lists.debian.org

Hello,

on ppc64 Firefox crashes on startup with wasm sandboxing enabled:

#0  0x00007fff8ad96d5c in ?? () from /lib/powerpc64-linux-gnu/libc.so.6
--Type <RET> for more, q to quit, c to continue without paging--
[Current thread is 1 (Thread 0x7fff8b474da0 (LWP 1421763))]
(gdb) bt
#0  0x00007fff8ad96d5c in ?? () from /lib/powerpc64-linux-gnu/libc.so.6
#1  0x00007fff8ad32834 in raise () from /lib/powerpc64-linux-gnu/libc.so.6
#2  0x00007fff80b83704 in nsProfileLock::FatalSignalHandler (signo=11, 
info=<optimized out>, context=0x7fffed50e0d0)
    at ./toolkit/profile/nsProfileLock.cpp:177
#3  <signal handler called>
#4  i32_load8_u (mem=<optimized out>, addr=2016478208) at rlbox.wasm.c:146
#5  w2c_rlbox_streqci (var_p0=var_p0@entry=262000, var_p1=2016478208, 
instance=<optimized out>) at rlbox.wasm.c:55615
#6  0x00007fff7b2e78e8 in w2c_rlbox_getEncodingIndex (instance=<optimized out>, 
var_p0=<optimized out>) at rlbox.wasm.c:55548

This can be fixed by disabling wasm sandboxing similar to s390x [1]. Thus, 
please
disable wasm sandboxing on ppc64 (see attached patch). Might even be a good idea
to disable it for all big-endian targets.

Thanks,
Adrian

> [1] 
> https://salsa.debian.org/mozilla-team/firefox/-/commit/c2a4ff612f4492182951be6055d088db9488e92d

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- debian/browser.mozconfig.in.orig    2025-05-10 13:56:10.768539645 -0700
+++ debian/browser.mozconfig.in 2025-05-10 10:44:18.060482533 -0700
@@ -30,6 +30,6 @@
 ac_add_options --with-unsigned-addon-scopes=app,system
 ac_add_options --allow-addon-sideload
 ac_add_options --enable-alsa
-%if DIST == bullseye || DEB_HOST_ARCH == s390x
+%if DIST == bullseye || DEB_HOST_ARCH == s390x || DEB_HOST_ARCH == ppc64
 ac_add_options --without-wasm-sandboxed-libraries
 %endif

Reply via email to