joex92,
Suggestions . . .
Open 2 Terminal.app windows.
In Terminal window 1, enter:
top -o +command -O +pid -stats command,cpu,state,rsize,pid
In Terminal window 2, enter:
open -a “Brave Browser.app” -n --args --disable-gpu --enable-leak-detection --crash-on-failure --incognito
That command will start Brave Browser with Hardware Aceleration DISABLED, and using a New Private Window.
If Brave Browser runs long enough, so that you can look at its appearance in Terminal window 1, that may interest.
If / when Brave Browser crashes, Terminal window 1 may interest - again, maybe.
All your Apple Mac OS Crash Reports point to
Identifier: com.brave.Browse [the Brave Browser]
Crashed Thread: ThreadPoolForegroundWorker
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Reference:
[Apple - Developer:] Understanding the Exception Types in a Crash Report:
“https://developer.apple.com/documentation/xcode/understanding-the-exception-types-in-a-crash-report”
A portion of that, in detail [I dis-assembled Apple’s paragraphs, so I could read it more easily]:
EXC_BREAKPOINT (SIGTRAP) . . .
The breakpoint exception type indicates a trace trap interrupted the process. A trace trap gives an attached debugger the chance to interrupt the process at a specific point in its execution.
On ARM processors, this appears as ‘EXC_BREAKPOINT (SIGTRAP).’ On ‘x86_64’ processors, this appears as ‘EXC_BAD_INSTRUCTION (SIGILL)’.
The Swift runtime uses trace traps for specific types of unrecoverable errors — see
[Addressing Crashes from Swift Runtime Errors]
“https://developer.apple.com/documentation/xcode/addressing-crashes-from-swift-runtime-errors”
for information on those errors.
Some lower-level libraries, such as
[Dispatch]
“https://developer.apple.com/documentation/dispatch”
trap the process with this exception upon encountering an unrecoverable error, and log additional information about the error in the ‘Additional Diagnostic Information’ section of the crash report.
See
[Diagnostic Messages]
“https://developer.apple.com/documentation/xcode/examining-the-fields-in-a-crash-report#Diagnostic-Messages”
for information about those messages.