[tor-bugs] #21804 [Applications/Tor Browser]: Tor Browser refuses to start with <jemalloc>: Corrupt redzone 0 bytes after 0x7f0503ede9d0 (size 80), byte=0x0

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Jun 9 14:29:58 UTC 2017


#21804: Tor Browser refuses to start with <jemalloc>: Corrupt redzone 0 bytes after
0x7f0503ede9d0 (size 80), byte=0x0
--------------------------------------+--------------------------
 Reporter:  adrelanos                 |          Owner:  tbb-team
     Type:  defect                    |         Status:  closed
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:  wontfix
 Keywords:                            |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------
Changes (by gk):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Replying to [comment:6 adrelanos]:
 > 6.5a6
 >
 > * Qubes Debian stretch based AppVM: works
 > * VirtualBox Debian stretch: works
 > * VirtualBox Whonix Debian stretch based VM: broken
 > * Qubes-Whonix Debian stretch based AppVM: broken
 >
 > "Some setting that Whonix changes or package that Whonix does (not)
 install is triggering this issue." (No recompiled packages.) Any advice on
 narrow it down more than that?

 Unfortunately, not. We won't ship Tor Browser with jemalloc4 anymore as
 Mozilla has indicated that they won't use it in the future. Thus, this bug
 is somewhat moot and I'll close it as WONTFIX. (Might still be interesting
 to understand why this happens in the first place at all)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21804#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list