[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
Thu Mar 23 11:30:54 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:  new
     Priority:  Medium                    |  Milestone:
    Component:  Applications/Tor Browser  |    Version:
     Severity:  Normal                    |   Keywords:
Actual Points:                            |  Parent ID:
       Points:                            |   Reviewer:
      Sponsor:                            |
------------------------------------------+----------------------
 Since Tor Browser {{{7.0a2}}} it does no longer start. (Debian stretch
 based Qubes-Whonix 14)

 {{{
 user at 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 at host:~/.tb/tor-browser$ echo $?
 139
 }}}

 Something in the system config or environment seems to trigger this. Any
 idea?

 Related:
 #10281

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


More information about the tor-bugs mailing list