Brave crashes upon launching on MacBook


#1

Hi all,

i. Operating system: MacOS High Sierra 10.13.4
ii. Your Brave Version 0.22.727

Example:
- i. I downloaded and installed Brave.
- ii. I open Brave
- iii. Pops up with Ready to Make Brave your default browser? then just keeps loading and nothing happens.

Apologies, I’m not tech savvy, please let me know if you require any additional information?


#2

Hi @BigT

If you installed Brave in the default location (your Applications folder), could you try this:

  1. make sure Brave is closed
  2. Open up your Terminal
  3. Copy/paste this into the terminal and hit return:

LEDGER_VERBOSE=true /Applications/Brave.app/Contents/MacOS/Brave

  1. Brave will launch and you’ll probably experience the issue you described. However, in the terminal you will see some information (messages, possibly errors).
  2. Could you let this run for a minute or two (enough to see your issue), and copy/paste the info from the terminal either into a response here or you can private message the info to me if you’d prefer. (Just click on my name and then you’ll see a blue Message button to open up a message with me).

Thanks,
Lauren


#3

Crash reporting enabled

starting up ledger publisher integration

starting up ledger client integration
<<< GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/timestamp
<<< content-type: application/json; charset=utf-8
<<< user-agent: Brave/0.22.727 Chrome/66.0.3359.170 Muon/6.0.12 macOS x64
<<< accept-encoding:
<<<
[ response for GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/timestamp ]

HTTP/1.1 200
accept-ranges: bytes
cache-control: private
connection: keep-alive
content-length: 35
content-type: application/json; charset=utf-8
date: Sat, 09 Jun 2018 09:57:30 GMT
server: Cowboy
strict-transport-security: max-age=31536000
vary: accept-encoding
via: 1.1 vegur
x-rate-limit-limit: 9007199254740991
x-rate-limit-remaining: 9007199254740990
x-rate-limit-reset: 1528538251

{“timestamp”:“6565021777255202817”}
<<< GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/identity?publisher=brave.com
<<< content-type: application/json; charset=utf-8
<<< user-agent: Brave/0.22.727 Chrome/66.0.3359.170 Muon/6.0.12 macOS x64
<<< accept-encoding:
<<<
[1692:775:0609/105731.075391:ERROR:CONSOLE(27)] “(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.”, source: chrome://brave/Applications/Brave.app/Contents/Resources/app.asar/app/extensions/brave/gen/app.entry.js (27)
[ response for GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/identity?publisher=brave.com ]

HTTP/1.1 200
accept-ranges: bytes
cache-control: private
connection: keep-alive
content-length: 159
content-type: application/json; charset=utf-8
date: Sat, 09 Jun 2018 09:57:31 GMT
server: Cowboy
strict-transport-security: max-age=31536000
vary: accept-encoding
via: 1.1 vegur
x-rate-limit-limit: 9007199254740991
x-rate-limit-remaining: 9007199254740935
x-rate-limit-reset: 1528538250

{“SLD”:“brave.com”,“RLD”:"",“QLD”:"",“publisher”:“brave.com”,“properties”:{“facet”:“domain”,“exclude”:true,“tags”:[“brave”],“timestamp”:“6397818803501141554”}}
<<< GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/identity?publisher=youtube.com
<<< content-type: application/json; charset=utf-8
<<< user-agent: Brave/0.22.727 Chrome/66.0.3359.170 Muon/6.0.12 macOS x64
<<< accept-encoding:
<<<
[1692:775:0609/105731.135884:ERROR:CONSOLE(27)] “(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.”, source: chrome://brave/Applications/Brave.app/Contents/Resources/app.asar/app/extensions/brave/gen/app.entry.js (27)
<<< GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/identity?publisher=google.co.uk
<<< content-type: application/json; charset=utf-8
<<< user-agent: Brave/0.22.727 Chrome/66.0.3359.170 Muon/6.0.12 macOS x64
<<< accept-encoding:
<<<
[1692:775:0609/105731.339785:ERROR:CONSOLE(27)] “(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.”, source: chrome://brave/Applications/Brave.app/Contents/Resources/app.asar/app/extensions/brave/gen/app.entry.js (27)
2018-06-09 10:57:31.579 Brave Helper[1698:152068] Couldn’t set selectedTextBackgroundColor from default ()
[ response for GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/identity?publisher=youtube.com ]

HTTP/1.1 200
accept-ranges: bytes
cache-control: private
connection: keep-alive
content-length: 164
content-type: application/json; charset=utf-8
date: Sat, 09 Jun 2018 09:57:32 GMT
server: Cowboy
strict-transport-security: max-age=31536000
vary: accept-encoding
via: 1.1 vegur
x-rate-limit-limit: 9007199254740991
x-rate-limit-remaining: 9007199254740930
x-rate-limit-reset: 1528538252

{“SLD”:“youtube.com”,“RLD”:"",“QLD”:"",“publisher”:“youtube.com”,“properties”:{“facet”:“SLD”,“exclude”:true,“tags”:[“platforms”],“timestamp”:“6523363880133984257”}}
[ response for GET https://mercury-proxy.privateinternetaccess.com/v3/publisher/identity?publisher=google.co.uk ]

HTTP/1.1 200
accept-ranges: bytes
cache-control: private
connection: keep-alive
content-language: uk
content-length: 163
content-type: application/json; charset=utf-8
date: Sat, 09 Jun 2018 09:57:32 GMT
server: Cowboy
strict-transport-security: max-age=31536000
vary: accept-encoding
via: 1.1 vegur
x-rate-limit-limit: 9007199254740991
x-rate-limit-remaining: 9007199254740952
x-rate-limit-reset: 1528538252

{“SLD”:“google.co.uk”,“RLD”:"",“QLD”:"",“publisher”:“google.co.uk”,“properties”:{“facet”:“SLD”,“exclude”:true,“tags”:[“search”],“timestamp”:“6386968242937659396”}}
<<< GET https://ledger.mercury.basicattentiontoken.org/v1/publisher/ruleset?consequential=true
<<< content-type: application/json; charset=utf-8
<<< user-agent: Brave/0.22.727 Chrome/66.0.3359.170 Muon/6.0.12 macOS x64
<<< accept-encoding:
<<<
[ response for GET https://ledger.mercury.basicattentiontoken.org/v1/publisher/ruleset?consequential=true ]

HTTP/1.1 200
accept-ranges: bytes
cache-control: private
connection: keep-alive
content-length: 36
content-type: text/plain; charset=utf-8
date: Sat, 09 Jun 2018 09:57:33 GMT
etag: “04ea5303c87165cf6d0745b80b20468441090156”
last-modified: Thu, 07 Jun 2018 22:48:57 GMT
server: Cowboy
vary: accept-encoding
via: 1.1 vegur
x-rate-limit-limit: 60
x-rate-limit-remaining: 59
x-rate-limit-reset: 1528538313

go away

User-agent: *
Disallow: /

ledger client callback: clientP=true errP=false resultP=true delayTime=60000

ledger client run: clientP=true delayTime=60000
publisher blockedP stickyP verified excluded eligibleP visibleP contribP duration visits


#4

Hi @BigT

Thanks for trying that! Nothing is jumping out at me as a problem, so I’ve shared with development and logged an issue:

Thanks,
Lauren


#5

@LaurenWags Thanks! I’ve noticed the issue you’ve linked is closed, does this mean the problem is resolved? :slight_smile:


#6

Hey @BigT

If you look at the issue you should see a milestone assigned - which in the case above is for 0.23.x. So hopefully, this issue will be included in our next release if testing goes well :slight_smile:

Thanks,
Lauren


#7

Wow - thank you @LaurenWags for the swift response! :slight_smile: And again, much appreciated for clarifying, I wasn’t too sure what it meant. Enjoy your weekend!


#8

If you delete the Brave folder found in the Application Support folder. Do a reinstall and things should be alright.

The application support folder can be found by ~/Library/Application Support in Finder>Go>Go to Folder - just in case you did not know where it was.


#9

The only thing I might add to your description @v0iD is that if you don’t have the backup words for your Brave wallet (and it contains BAT), don’t delete your folder because then your wallet/BAT are gone. You can rename/move the brave profile folder you mention in order to preserve this info.


#10

@BigT no problem! The fix will be available on the beta channel, I can give you some instructions if you want to give it a try on that version. Let me know!

Lauren


#11

Edit: Actually, I’ll just wait for the next release :slight_smile:


#12

@BigT Alternatively you can do what I mentioned. With the knowledge like @LaurenWags said about losing your current wallet unless you have backed it up.

I know from experience that it does work afterwards.


#13

@bigT if you change your mind let me know but no pressure :slight_smile:


#14