Tor Browser refuses to start with <jemalloc>: Corrupt redzone 0 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
Since Tor Browser 7.0a2
it does no longer start. (Debian stretch based Qubes-Whonix 14)
user@host:~/.tb/tor-browser$ ./start-tor-browser.desktop --debug
Launching './Browser/start-tor-browser --detach --debug'...
Using system Tor process.
<jemalloc>: Corrupt redzone 0 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 1 byte after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 2 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 3 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 4 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 5 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 6 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
<jemalloc>: Corrupt redzone 7 bytes after 0x7f0503ede9d0 (size 80), byte=0x0
./Browser/start-tor-browser: line 368: 2593 Segmentation fault TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null
user@host:~/.tb/tor-browser$ echo $?
139
Something in the system config or environment seems to trigger this. Any idea?
Related: legacy/trac#10281 (moved)