Confirmed same behavior with Nightly, both activating while Brave is open and before opening Brave 1.5.77 Chromium: 80.0.3987.66 (Official Build) nightly (64-bit) on macOS Version 10.15.2 (Build 19C57)@Mattches, any insight?
Errors I get in system.log are:
Activating while Brave open: Feb 4 10:11:47 HnkAir com.apple.xpc.launchd (com.brave.Browser.nightly.8680): Service exited due to SIGILL | sent by exc handler
Activating before opening Brave: Feb 4 10:19:59 HnkAir com.apple.xpc.launchd (com.brave.Browser.nightly.8680): Service exited due to SIGSEGV | sent by exc handler
Would anyone encountering this issue be willing to share a short recording of the behavior? I’m unable. to reproduce it but I have a feeling I’m performing the wrong steps to do so – would be helpful to see the behavior in action.
So, it happens later, now, @Mattches . Video was a little big so I put it on my Google Drive. I can turn on the keyboard without Nightly or Release crashing, but as soon as I enter a URL with it and hit return, they both crash and won’t reopen until the keyboard is deactivated.
Thanks for the recording – I see the issue now and can reproduce it on what seems like all Brave builds. I’ll be filing an issue for this today and will drop the link in this thread when it’s done.
brought me here but since my issues is not related to the Accessibility issue may I ask you whether my issues have any attention by the Developers?
It seems to me that both @Aa-ron and @steeven ave too many other things to do (than responding to my many requests for a feedback)!
And I can’t get the constant crashing fixed!
Welcome, @MDub777, and take heart. It looks like this should be resolved before too long.
Checking the GitHub Issue noted above, it was labeled as waiting for upstream fix, meaning that it’s a Chromium issue, not just a Brave issue, IIUC (@Mattches, is that right?).
I tried the Keyboard Viewer with my install Chromium 82.0.4079.0 (Developer Build) (64-bit), and it seems to work fine. Tellingly, when I clicked on my Brave Nightly open behind the Chromium window, Brave crashed. My Brave Nightly is Brave 1.8.53 Chromium: 81.0.4044.83 (Official Build) nightly (64-bit). So this issue should be resolved at least as soon as 82.0.4079.0 hits the Brave chain, maybe with an even closer version. If I get a chunk of time, I’ll try something as close to 82 as I can find.
That is correct – I believe I’ve seen other Chrome/Chromium users reporting the same issue so it’s likely an issue with the underlying engine. So yes, as you said, this issue should be resolved soon.