You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v0.4.8.19 Crashes when start/stop more then once. #94
When my app goes into the background I force Tor to quit and when it reenters the foreground it reboots. Previously this worked fine without any crashes.
Now I notice that if Tor.framework v0.4.8.19 is forced to quit and reboot more than once it crashes my app with an ugly error:
warning: Tor was compiled with optimization - stepping may behave oddly; variables may not be available.Can't show file for stack frame : <DBGLLDBStackFrame: 0x3518b0e70> - stackNumber:0 - name:worker_thread_main [inlined]. The file path does not exist on the file system: /var/folders/mr/lw68m7t562z9sccvfy8qrdwc0000gn/T/tmp.4cWhf2K5l2/tor/src/lib/evloop/workqueue.c
warning: Tor was compiled with optimization - stepping may behave oddly; variables may not be available.Can't show file for
stack frame : <DBGLLDBStackFrame: 0x3518b0e70> - stackNumber:0 - name:worker_thread_main [inlined]. The file path
does not exist on the file system:
/var/folders/mr/lw68m7t562z9sccvfy8qrdwc0000gn/T/tmp.4cWhf2K5l2/tor/src/lib/evloop/workqueue.c
That's just a message from the debugger, meaning, the debugger is sorry for not being able to show you code instead of memory addresses and opcodes. (Because you use production builds, which don't have debugging information attached.)
Anyway, these are the referenced code pieces from your screenshot:
Activity
tladesignz commentedon Nov 18, 2025
Maybe it's this problem?
guardianproject/orbot-android#1479 (comment)
I released 0.4.8.20 yesterday. Is it still a problem?
Fonta1n3 commentedon Nov 19, 2025
Thank you, will test and revert back soon.
Fonta1n3 commentedon Nov 19, 2025
Can confirm the issue remains, same error message, same crash.
tladesignz commentedon Nov 25, 2025
Just released a 0.4.8.21 build. Still the same?
Fonta1n3 commentedon Nov 25, 2025
Just tried and yes I am still getting a crash:
tladesignz commentedon Nov 25, 2025
That's just a message from the debugger, meaning, the debugger is sorry for not being able to show you code instead of memory addresses and opcodes. (Because you use production builds, which don't have debugging information attached.)
Anyway, these are the referenced code pieces from your screenshot:
Fonta1n3 commentedon Nov 25, 2025
If there is anything more i can provide to help debug please let me know.
I'll just downgrade for now.
tladesignz commentedon Nov 25, 2025
So, just to be clear: .18 was fine?
Would it be possible for you to
git bisectthis?You would need to check out
Tor.frameworkand reference the local checkout from your project.Here's a patch for
build-xcframework.sh, so you only build the minimum (no LZMA, only iOS arm64 real device binaries):Fonta1n3 commentedon Nov 26, 2025
Good question, let me test more and make sure that is the case.