Mac OS - Turning On Keyboard Viewer Crashes Brave

[iREDMe]

Description of the issue: When Brave is open, and you show the keyboard viewer, Brave mysteriously crashes for no apparent reason.
How can this issue be reproduced?

1. Have Brave open.
2. System Preferences -> Keyboard -> “Show keyboard and emoji viewers in menu bar”)
3. Turn on Keyboard Viewer from menu bar.

Expected result: Brave crashes in a suffering crash.

Brave Version: Version 1.1.23 Chromium: 79.0.3945.88 (Official Build) (64-bit)

Additional Information: Mac OS v10.15.2 (Catalina)

[megaspaz]

Just a data point… I don’t see this behavior at all with Brave on Mojave…

[Alexander1981]

Почему не могу запустить Браве храбрый в хроме

[smchk]

I am also getting this consistently on two mac laptops with same versions.

[aphoid]

I am seeing this behavior on a Macbook Pro running Brave 1.2.42 Chromium 79.0.3945.117 on macOS Catalina 10.15.2.

update: the crash persists on Brave 1.2.43 Chromium 79.0.3945.130

[Bravitz]

I see this too. Trying to learn new language, nice to have keyboard viewer up as a reference.

OS: MacOS Catalina 10.15.2.
Brave Version: Version 1.2.42 Chromium: 79.0.3945.117 (Official Build) (64-bit)

Here is link to a pastebin with the crash log:
https://pastebin.com/BH3WHHiD

[hnktong]

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[1] (com.brave.Browser.nightly.8680[70991]): Service exited due to SIGILL | sent by exc handler[70991]

Activating before opening Brave:
Feb 4 10:19:59 HnkAir com.apple.xpc.launchd[1] (com.brave.Browser.nightly.8680[71286]): Service exited due to SIGSEGV | sent by exc handler[71286]

Doesn’t appear to be a crash log.

[jakub]

Same here on Catalina 10.15.3, with both

Brave Dev
[Version 1.4.76 Chromium: 79.0.3945.130 (Official Build) dev (64-bit)]

Brave
[Version 1.2.43 Chromium: 79.0.3945.130 (Official Build)]

[Mattches]

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.

[hnktong]

@Mattches

Would anyone encountering this issue be willing to share a short recording of the behavior?

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.

OS	macOS Version 10.15.3 (Build 19D76)
Brave 1.6.14 Chromium: 80.0.3987.87 (Official Build) nightly (64-bit)
Brave 1.3.115 Chromium: 80.0.3987.87 (Official Build) (64-bit)

[Mattches]

@hnktong,
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.

[Mattches]

Whoops – I lied. Looks like there’s already an issue filed and the team already has eyes on it

macOS Digital Keyboard's Enter key crashes Brave

[pixi]

@Mattches : These topic

Brave on macOS crashes regularly

Hi folks, as requested just the facts: Description of the issue: Brave was crashing by itself after ~a day of working fine. This happens in the evening (20:00 - 21:00 CET). Restarting just shows me the warning whether the previous window should be re-opened and crashes again. Recently it started to crash by itself also during the day. I couldn’t find a scheme in it (not on the same websites, no special action (sync etc.) Steps to Reproduce (add as many as necessary): 1. 2. 3. Not possible '…

Brave on macOS crashes regularly - Still!

Hi guys, I appreciate your work and effort you put into this app. And I am aware that you have to be quite busy handling this and further development. What REALLY disappoints me nonetheless is that you stop responding here: Brave on macOS crashes regularly although feedback as reqested was provided, as well as to personal messages! It seems to me that you don’t have a solution for the constant crashing and, with all the reports send, can’t figure out what’s wrong! While I could understand if …

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!

[Mattches]

@pixi,
As I said in my last reply:

Mac OS - Turning On Keyboard Viewer Crashes Brave

Whoops – I lied. Looks like there’s already an issue filed and the team already has eyes on it

[Desktop] macOS Digital Keyboard's (accessibility keyboard) crashes Brave

[MDub777]

Same issue continues for macOS Catalina.

Description of Issue: When Brave is open and “Show Keyboard Viewer” is selected, entering a url and hitting enter causes Brave to crash.

Steps to Reproduce:

1. Open Brave
2. Click on language icon in top right of the OS menu bar
3. Select “Show Keyboard Viewer”
4. Type address into Brave and hit Enter

Expected result: Brave crashes

Brave Version: 1.5.115 Chromium: 80.0.3987.149 (Official Build) (64-bit)

macOS Version: Catalina 10.15.4 (19E266)

[hnktong]

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.

[Mattches]

@hnktong,
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.