“The process seems get killed before main function call”
Which makes it hard to grab a log entry.
I get the same result on a device running 10.14.6 which makes me think that recent os security hardening like notarization checks and tcc aren’t the problem. The bridge in the nightly isn’t at fault either because removing it doesn’t help. Perhaps it’s the dylib? I have no idea.
On my M1 device I added the nightly rather than overwriting the current tbb. When I uninstalled the nightly the current stable build of tor browser behaved the same way such that I had to completely remove the browser (at least the application support folder) and reinstall in order to get it to work again.
Perhaps there would be something diagnostic in the system log but my skills with Consol aren’t good enough to figure out how to capture that. It would be very noisy I’m sure.
Howard Oakley at eclecticlight.com has a couple of log browser utilities which simplify capturing log streaming. I’ll see if I can make any progress with one of them.
Overall, it really does seem like a bug in the nightly. Maybe Dan Ballard could be persuaded to have a look.
MarkC
···
On Nov 10, 2025, at 2:59 PM, Shelikhoo via Tor Project Forum noreply@forum.torproject.org wrote:
The process seems get killed before main function call
Mark Charnell
markcharn3ll@icloud.com
604-725-2133 mobile