Another test, if you are willing . . .
Quit Brave Browser.
How about moving both folders:
- mnojpmjdmbbfmejpflffifhffcmidifd
- LevelDB
/Users/username_aka_shortname/Library/Application Support/BraveSoftware/Brave-Browser/Default/Local Extension Settings/mnojpmjdmbbfmejpflffifhffcmidifd
and
/Users/username_aka_shortname/Library/Application Support/BraveSoftware/Brave-Browser/Default/Sync Data/LevelDB
. . . to the Desktop. Restart the Mac. Use Brave Browser for a short while. (I am guessing that both folders will be replaced by new folders.) Quit and then Start Brave Browser.
That last Start, is when trouble would occur, if any.
BTW, try - for testing - to use New Windows, instead of tabs; and if willing, New Private Windows. The reason is, because there is some relation between the Brave Browser Sync v2 bug and tabs.
–
Meanwhile, @ZiG-ZaG and @CiscoCampos have reported, that removing the “BraveSoftware” folder
/Users/username/Library/Application Support/BraveSoftware
. . . fixed the problem.
Also @jelacou :
–
UPDATE Monday, 20220307
With release of Brave Browser v.1.36.111 (Chrome 99.0.4844.51) – re Chrome release notes contain info regarding a significant Chrome (for MacOS) installation bug (id=1300598) affecting late model Mac “arm64 users”:
The author is Mark Mentovai. Briefly:
When the main executable is updated on disk while the application is running, and the offset of the Mach-O image at the main executable’s path changes from the offset that was determined when the executable was loaded, SecCode ceases to be able to work with the executable. This may be triggered when the product is updated on disk but the application has not yet relaunched.
The proposed fixing, involves “[structure] padding” – filling in space(s) in code, in order to fix structure alignment. (If I read the info, correctly?)
I wonder, if the bug (id=1300598) has been a source of trouble for the many recent (winter 2021-2022) Mac and/or Brave Browser crashes.
Ref.: “https://bugs.chromium.org/p/chromium/issues/detail?id=1300598”
–