Tor (0.4.3.5) Occasionally crashes with these stack offsets #65

Activity

1. tladesignz commented on May 28, 2020

   

   tladesignz

   on May 28, 2020

   Member

   More actions

   Interesting. It would be great, if you could re-symbolicate that crashlog.
2. ProofOfKeags commented on May 28, 2020

   

   ProofOfKeags

   on May 28, 2020

   Author

   More actions

   K. I'll look into it. I've never done that before, if you have any advice I'd appreciate it. Otherwise I'll see what I can do. I think this is an underlying issue in the tor binary as opposed to an issue with Tor.framework but I suppose we can't determine that without recovering the symbols.
3. ProofOfKeags commented on May 28, 2020

   

   ProofOfKeags

   on May 28, 2020

   Author

   More actions

   Thread 10 name:  Tor
   Thread 10 Crashed:
   0   libsystem_kernel.dylib        	0x00000001b80f6df0 __pthread_kill + 8
   1   libsystem_pthread.dylib       	0x00000001b8016930 pthread_kill + 228
   2   libsystem_c.dylib             	0x00000001b7fa48b4 abort + 104
   3   Tor                           	0x00000001032bf780 0x102f20000 + 3798912
   4   Tor                           	0x00000001030ba000 format_hex_number_sigsafe + 1679360 (torerr.c:299)
   5   Tor                           	0x00000001030b515c tor_mutex_new + 1659228 (compat_mutex.c:18)
   6   Tor                           	0x00000001030506f4 pubsub_connect + 1246964 (main.c:1208)
   7   Tor                           	0x0000000103050820 tor_run_main + 1247264 (main.c:1249)
   8   Tor                           	0x0000000102f2be44 -[TORThread main] + 48708 (TORThread.m:73)
   9   Foundation                    	0x00000001b87097a0 __NSThread__start__ + 864
   10  libsystem_pthread.dylib       	0x00000001b80158fc _pthread_start + 168
   11  libsystem_pthread.dylib       	0x00000001b801d9d4 thread_start + 8
   
4. tladesignz commented on Jun 5, 2020

   

   tladesignz

   on Jun 5, 2020

   Member

   More actions

   Sorry, for the delay! Great work, and thanks for reporting it!

   That's clearly inside Tor. I'll have somebody from Tor look at this.

   👍React with 👍1Reacted by Fully Noded
5. tladesignz commented on Jun 5, 2020

   

   tladesignz

   on Jun 5, 2020

   Member

   More actions

   @ahf, can you take a look at this? Thanks!

   👍React with 👍1Reacted by Fully Noded
6. Fonta1n3 commented on Jun 5, 2020

   

   Fonta1n3

   on Jun 5, 2020

   More actions

   Just wanted to chime in and second that i am experiencing the same issue.
7. ahf commented on Jun 22, 2020

   

   ahf

   on Jun 22, 2020

   More actions

   How do I reproduce this issue? I haven't seen it yet with Tor 0.4.3.5 in OnionBrowser when I test it there.
8. ProofOfKeags commented on Jun 22, 2020

   

   ProofOfKeags

   on Jun 22, 2020

   Author

   More actions

   Unfortunately I haven't been able to consistently get it to happen in response to a particular action. However it does happen semi-often within the Embassy App. if you want to test it out we can give you the creds to our test server, although if you're interested I encourage you to get one ;).
9. tladesignz commented on Sep 28, 2020

   

   tladesignz

   on Sep 28, 2020

   Member

   More actions

   I released a Tor.framework based on Tor 0.4.4.5 recently. If anybody can report this problem still occurring with the latest version, I'm happy to accept re-openings. If not, I'm considering this done, as @ahf told me, that this is in a part which got reworked with recent Tor versions.
10. tladesignz

    closed this as completedon Sep 28, 2020