Trying to login to a website that I often login to. Brave browser gives me an error message, yet Brave browser nightly build doesn’t ??
There are no parameters used for Brave browser, but the nightly build has these:
brave-browser-nightly -n --args --incognito --no-experiments --disable-extensions --disable-gpu --enable-leak-detection --crash-on-failure 2> $HOME/Desktop/brave_console_out.txt
so, should I simply run Brave browser with those parms ? Then send the log to ..?
Msg is attached
I have now run brave browser as follows:
brave-browser -n --args --incognito --no-experiments --disable-extensions --disable-gpu --enable-leak-detection --crash-on-failure 2> $HOME/Desktop/brave_console_out.txt
The bug still appears, showing the error message. ..
[4903:4994:0916/071351.954538:ERROR:content/browser/browser_main_loop.cc:286] GLib: g_main_context_pop_thread_default: assertion ‘stack != NULL’ failed
[4903:4993:0916/071351.955292:ERROR:content/browser/browser_main_loop.cc:286] GLib: g_main_context_pop_thread_default: assertion ‘stack != NULL’ failed
[4903:4992:0916/071351.955797:ERROR:content/browser/browser_main_loop.cc:286] GLib: g_main_context_pop_thread_default: assertion ‘stack != NULL’ failed
[4903:4903:0916/071423.570507:ERROR:content/browser/renderer_host/render_process_host_impl.cc:6330] Terminating render process for bad Mojo message: Received bad user message: No binder found for interface blink.mojom.WebOTPService for the frame/document scope
[4903:4903:0916/071423.570547:ERROR:content/browser/bad_message.cc:29] Terminating renderer for bad IPC message, reason 123
[0916/071423.589236:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0916/071423.590698:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0916/071423.590956:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0916/071423.591151:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0916/071423.596150:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0916/071423.597114:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0916/071423.598389:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0916/071423.598419:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0916/071423.604544:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0916/071423.604563:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0916/071423.604590:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0916/071423.604603:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
and it would appear the crash report details have been sent (see attachment). So it appears there is noting else I can do, is that correct ?
Either something in Nightly has fixed this issue and the fix hasn’t made its way through to release channel yet or there’s still something contained within your Brave (stable) profile.
Can you test again with a fresh profile in the stable builds (make sure you close your original profile window first) and see if you get the same results?
Yes, the error definitely doesn’t happen with the nightly build. Plus it is only one website, attempting a login, where they do two factor authentication.
It appears I don’t have (or use ??) a profile at all. When I search for ‘profile’ under the stable build, the prompt is to open a Brave account. I have a forum account only. Plus there is no profile showing.
Yeah I was referring to a browser profile here. You can create an additional one by launching Brave and going to Main Menu > More tools > Add profile (you can delete this profile after testing).
Additionally, can you share the website you’re trying to login to so I can test on my end? If it’s sensitive in nature I can send you a DM where you can share the site with me if you’d rather.
Okay thanks. I’ll add the profile and test.
@Mattches yes thanks, a DM please.
@jehoshua7 thank you for sharing in the DM.
Were you able to test with a fresh profile?
Not yet, things to do. I considered this though - if I currently don’t have a profile, how will a new one make a difference ?? Anyhoo, I can do that this afternoon (Australia).
There is a Default profile path created when you first launch the browser that stores all your data, which is what you’re using now. So you do have a profile, it’s just not listed in the profile menu because it’s the only one you have.
Okay, so I created a new profile and used that on the same site/login…same error message unfortunately. As you say, there is some ‘fix’ for this in the nightly build, as it doesn’t happen when I use a Brave nightly build.
I’ll just use the nightly build for that website, for now, thanks for your help.
As I noticed a Brave browser update this morning, have again tried to login to that site, but without success. Same message. I tried 2 different profiles.
By the ../Completed path within the Crash Reports path, it appears that the reports have been sent.
Brave 1.95.102 (Official Build) (x86_64)
Chromium: 153.0.8010.48
The ‘nightly’ build, which didn’t result in the error message is:
Brave 1.97.27 (Official Build) nightly (x86_64)
Chromium: 153.0.8010.37
I would have assumed on a brave-browser update, it would have incorporated all the ‘nightly’ build, but the version number differences hint otherwise.
In the new profile did you have the same flags enabled as you did originally?
I can’t see anywhere in the profile setup, on how to set flags ?
I found a post on the flags, it is brave://flags/ . I have none of these set, had no idea they were there.
Possibly you mean the parameters that are passed ? Like:
brave-browser-nightly -n --args --incognito --no-experiments --disable-extensions --disable-gpu --enable-leak-detection --crash-on-failure 2> $HOME/Desktop/brave_console_out.txt
@jehoshua7 yes sorry, I should I have been more clear. Those parameters you’re passing (the --args like --disable-extensions and --disable-gpu`) are all flags and I was curious if launching the browser without any of those params (flags) makes any difference?
@Mattches Just tested with new profile and Brave browser (not the nightly)..
Brave browser, no parameters, resulted in an the error msg when trying to login to that site (I shared with you.
Brave browser, with the parms, also resulted in the error msg when trying to login to the same site. Crash reports sent, and the o/p of the log file
===================
brave_console_out.txt
[3723:3723:0918/081157.079522:ERROR:chrome/browser/profiles/profile_attributes_storage.cc:1036] Failed to PNG encode the image.
[3723:3816:0918/081226.927084:ERROR:content/browser/browser_main_loop.cc:286] GLib: g_main_context_pop_thread_default: assertion ‘stack != NULL’ failed
[3723:3814:0918/081226.927095:ERROR:content/browser/browser_main_loop.cc:286] GLib: g_main_context_pop_thread_default: assertion ‘stack != NULL’ failed
[3723:3815:0918/081226.927455:ERROR:content/browser/browser_main_loop.cc:286] GLib: g_main_context_pop_thread_default: assertion ‘stack != NULL’ failed
[3723:3723:0918/081238.617516:ERROR:content/browser/renderer_host/render_process_host_impl.cc:6330] Terminating render process for bad Mojo message: Received bad user message: No binder found for interface blink.mojom.WebOTPService for the frame/document scope
[3723:3723:0918/081238.617560:ERROR:content/browser/bad_message.cc:29] Terminating renderer for bad IPC message, reason 123
[0918/081238.648581:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0918/081238.652672:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0918/081238.653199:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0918/081238.653535:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0918/081238.663728:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0918/081238.665670:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[0918/081238.668189:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0918/081238.668224:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0918/081238.678164:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0918/081238.678182:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0918/081238.678202:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
[0918/081238.678210:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
==========================
This is now working fine in the latest Brave browser.
Brave 1.95.104 (Official Build) (x86_64)
Chromium: 153.0.8010.53
Thanks @Mattches for all your help.
Interesting that Nightly works while the regular Brave build still crashes. hopefully those logs help pinpoint what’s different.
That’s not correct now. See the post at Aw, snap error message with Brave, but not with Brave nightly build - #17 by jehoshua7 , no mention of the nightly build.
It works now for both builds.
