sourcetree keeps crashing after upgrade to 4.1.1 - atlassian-sourcetree

I upgraded the source to latest version 4.1.1 but it keeps crashing whenever I click any repo after that. How can I fix it?
Process: Sourcetree [9208]
Path: /Applications/Sourcetree.app/Contents/MacOS/Sourcetree
Identifier: com.torusknot.SourceTreeNotMAS
Version: 4.1.1 (237)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Sourcetree [9208]
User ID: 501
Date/Time: 2021-06-16 12:30:58.563 -0400
OS Version: macOS 11.4 (20F71)
Report Version: 12
Anonymous UUID: D1F6D388-FE59-1547-31C8-BEF723D91654
Time Awake Since Boot: 230000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [9208]
VM Regions Near 0:
-->
__TEXT 10bc16000-10bf0e000 [ 3040K] r-x/r-x SM=COW /Applications/Sourcetree.app/Contents/MacOS/Sourcetree
Application Specific Information:
Performing #selector(localOutlineDoubleClick:) from sender STRepoBrowserBookmarkOutlineView 0x7fa54d044600
Any help is greatly appreciated

Same issue on an Intel Mac here.
I manually replaced the executable by the latest one from this page (4.1.9) and it solved the issue.

I downgrade the source tree version to 3.2.1 and it worked

Related

MySQLWorkbench crashes on macOS Big Sur 13.0.1 - Help Needed

I am a beginner in SQL and have been encountering an issue while running databases with MySQLWorkbench. The application crashes every time I try to launch it on my Mac, which has macOS Big Sur 13.0.1 (22A400) installed.
Process: MySQLWorkbench [3772]
Path: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier: com.oracle.workbench.MySQLWorkbench
Version: 8.0.32.CE (1)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 502
Date/Time: 2023-02-09 00:04:43.1666 +0100
OS Version: macOS 13.0.1 (22A400)
Report Version: 12
Bridge OS Version: 7.0 (20P420)
Anonymous UUID: 689E3614-BA3C-9F93-3852-F1EAEA383C46
Sleep/Wake UUID: 68C37724-2309-4EE6-81A3-2350C431CD35
Time Awake Since Boot: 15000 seconds
Time Since Wake: 8843 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [3772]
I have tried reinstalling the software, but the problem persists.

MySQLWorkbench Quit unexpectedly on macOS 12.6

Translated Report (Full Report Below)
Process: MySQLWorkbench [10215]
Path: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier: com.oracle.workbench.MySQLWorkbench
Version: 8.0.29.CE (1)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2022-09-18 01:13:02.9024 +0700
OS Version: macOS 12.6 (21G115)
Report Version: 12
Anonymous UUID: 93C12037-7AA4-2F17-6953-BD95C09A967C
Time Awake Since Boot: 8100 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Codes: 0x0000000000000001, 0x0000000000000008
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [10215]

Xcode crashes when adding a Swift package

When adding a swift package to a repo adding the package causes a crash.
Have you seen such a failure? What did you do?
Here is the stack trace:
PlugIn Identifier: libSwiftPM.dylib
PlugIn Version: ??? (17700)
Date/Time: 2021-04-17 14:02:53.780 +0100
OS Version: macOS 11.3 (20E5231a)
Report Version: 12
Bridge OS Version: 5.3 (18P54555a)
Anonymous UUID: E0A63D54-3439-6D85-7A26-1B18A623DBA6
Sleep/Wake UUID: 48028EAA-522A-4F9B-A1DB-08E369AB0C6B
Time Awake Since Boot: 94000 seconds
Time Since Wake: 44000 seconds
System Integrity Protection: enabled
Crashed Thread: 13 Dispatch queue: -[IDEExecutionEnvironment initWithWorkspaceArena:] (QOS: UNSPECIFIED)
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [49193]
Application Specific Information:
ProductBuildVersion: 12D4e
Workspace/Workspace.swift:1161: Fatal error: 'try!' expression unexpectedly raised an error: TSCBasic.GraphError.unexpectedCycle
In my case it was because I had the package before and I deleted it, but it's still in Derived Data. Clearing Derived data in /Users/<USER>/Library/Developer/Xcode/DerivedData/, then adding the swift package again fixes it.

unity 2017.4.15 crashing on export package

I have two unity versions(2017.4 and 2018.3.6) on mac book pro late 2013. both of unity crashes when i try to export package from any of the version.
A window appears which shows a long report copied below. how i can get rid from this
Process: Unity [591]
Path: /Applications/Unity 2017.4/Unity 2017.4.app/Contents/MacOS/Unity
Identifier: com.unity3d.UnityEditor5.x
Version: Unity version 2017.4.15f1 (2017.4.15f1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Unity [591]
User ID: 501
Date/Time: 2019-03-04 08:56:21.246 +0500
OS Version: Mac OS X 10.14.3 (18D109)
Report Version: 12
Anonymous UUID: CCFE4D87-8DFF-C67A-810F-F0C09D34F3EB
Time Awake Since Boot: 620 seconds
System Integrity Protection: enabled
Crashed Thread: 82 Dispatch queue: com.apple.root.user-interactive-qos.overcommit
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSGenericException', reason: 'NSRunAlertPanel may only be invoked from the main thread. Behavior on other threads is undefined.'
abort() called
terminating with uncaught exception of type NSException

iPhone SDK strange console message launchd_core_logic.c

I am running release version of the app on the iPhone, it works fine. There is no error messages in the XCode debugger:
Running…
Switching to thread 11779
Switching to thread 11779
sharedlibrary apply-load-rules all
(gdb) continue
Switching to thread 12291
Switching to thread 11779
Switching to thread 13059
Debugger stopped.
Program exited with status value:0.
However I see these messages in the console of iPhone when connect to it via Organizer:
WWed Oct 7 15:37:01 unknown com.apple.launchd[1] : (UIKitApplication:com.blah.blah[0x830c]) Bug: launchd_core_logic.c:2649 (23909):10
Wed Oct 7 15:37:01 unknown com.apple.launchd[1] : (UIKitApplication:com.blah.blah[0x830c]) Working around 5020256. Assuming the job crashed.
Wed Oct 7 15:37:01 unknown com.apple.launchd[1] : (UIKitApplication:com.blah.blah[0x830c]) Job appears to have crashed: Segmentation fault
Wed Oct 7 15:37:01 unknown com.apple.debugserver-43[6124] : 1 [17ec/1603]: error: ::read ( 7, 0x28091c, 1024 ) => -1 err = Bad file descriptor (0x00000009)
Wed Oct 7 15:37:01 unknown SpringBoard[25] : Application 'blah' exited abnormally with signal 11: Segmentation fault
I have tried Apple's UICatalog sample and empty view based app generated by the XCode. They both report exactly the same message as my code in the console. So this is NOT my app related.
There is no crash logs created, so I don't think it is a crash.
What is it? Is it a problem, even though application works perfectly fine?
Thanks
I had the same problem and it gave me problems when testing in app purchases. In the end I found out that I was running the program with an iPhone Distribution code signing instead of an iPhone Development code signing. When I changed that for the Debug configuration (and removed the Entitlements.plist) it worked again. Hope it helps.
It's not a problem. I have similar messages on my console all the time. And as you said it's not your apps fault, so as long as you app runs ok there is no problem.
The message is not from your app, it's from the com.apple.launchd. I think that only the xcode console output is really relevant for you.