I've rebooted, reinstalled and tried again but since SourceTree was updated yesterday it now won't launch at all. Here's the crash report:
Process: SourceTree  Path: /Applications/SourceTree.app/Contents/MacOS/SourceTree Identifier: com.torusknot.SourceTreeNotMAS Version: 220.127.116.11 (18.104.22.168) Code Type: X86-64 (Native) Parent Process: launchd  User ID: 501 Date/Time: 2015-11-18 09:17:35.542 +0000 OS Version: Mac OS X 10.8.5 (12F2560) Report Version: 10 Interval Since Last Report: 4667 sec Crashes Since Last Report: 213 Per-App Interval Since Last Report: 132 sec Per-App Crashes Since Last Report: 6 Anonymous UUID: B34695F2-A3EB-37B1-951A-A26E89592103 Crashed Thread: 8 Dispatch queue: com.apple.root.high-priority Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000038 VM Regions Near 0x38: --> __TEXT 0000000109646000-0000000109904000 [ 2808K] r-x/rwx SM=COW /Applications/SourceTree.app/Contents/MacOS/SourceTree Thread 0:: Dispatch queue: com.apple.main-thread
I've just now realised I have version 22.214.171.124 on my Yosemite partition and copied it over so it's all working again but there's clearly a showstopper bug in 126.96.36.199 for Mountain Lion users.
EDIT: I did paste the crash report above but my post was rejected for blacklisted words so...
Same here, v188.8.131.52 on OSX 10.9.5 crashes at startup. I've tried:
None of them helped.
I even tried to disassemble the binary with Hopper, but I didn't manage to find the address of the function that caused the crash, according to this callstack:
Thread 10 Crashed:: Dispatch queue: com.apple.root.high-priority 0 libdispatch.dylib 0x00007fff87829eeb dispatch_async_f + 3 1 com.torusknot.SourceTreeNotMAS 0x00000001008de732 0x1006f0000 + 2025266 2 com.torusknot.SourceTreeNotMAS 0x00000001008de678 0x1006f0000 + 2025080 3 libdispatch.dylib 0x00007fff8782728d _dispatch_client_callout + 8 4 libdispatch.dylib 0x00007fff87829885 _dispatch_source_invoke + 413 5 libdispatch.dylib 0x00007fff87828f87 _dispatch_root_queue_drain + 75 6 libdispatch.dylib 0x00007fff8782a177 _dispatch_worker_thread2 + 40 7 libsystem_pthread.dylib 0x00007fff884a5ef8 _pthread_wqthread + 314 8 libsystem_pthread.dylib 0x00007fff884a8fb9 start_wqthread + 13
Hoping for a quick fix ASAP.
Hi Everyone! Thanks for raising your concerns.
Yes, this is true, this is a known bug from this public issue on OS X. Please be sure to watch it, and vote on it, so that you're notified if this bug will be fixed in a future release.
For your reference, you can find our policy on how we prioritise feature and improvement requests at this page.
As for now, the workaround is to Wipe of SourceTree's Preference and restart SourceTree. Ensure that you have make a backup of the entire directory before doing so if needed. There is another alternative which is that you can download the previous version - SourceTree 184.108.40.206.
Hope that answers everyone's question! Please feel free to raise a ticket should you have any questions!
Exactly the same experience as Pete. Updated to 220.127.116.11 - crashed. Copied over 18.104.22.168, crashed again. Second attempt it launched. Updated again to 22.214.171.124 and this time it's working. I wouldn't have tried again though had I not read Pete's message so just re-iterating that this approach may work for others.
I didn't trust the auto-updater, so I renamed 126.96.36.199 (SourceTree Stable) and installed 188.8.131.52 alongside it. The new version does not crash right after launch for me now, so that's good. I hope it stays that way!
Update: I spoke too soon. After quitting once, it once again crashes almost immediately, just like 184.108.40.206 did, every time I try launching it again. 220.127.116.11 is still working fine, so I'm back to that release.
Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot