-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a new crash reporting endpoint #285
Comments
We'll just be re-using |
Yes, we will need to inspect the platform from the crash and send it to a different queue. cc @KarateCowboy |
Sounds like we'll use the endpoint |
Implemented by brave/vault-updater@4cf8e50 |
QA notes: Just make sure you can send a crash from about:crashes and that you can search for the ID. |
@srirambv pls post an issue for the 1.x backlog for ^ |
Sending crash reports does not work on Win7: #1188 |
@GeetaSarvadnya I think you need to enable it in chrome://settings/ first. The chrome://crashes/ page says that "Crash reporting is disabled" in that video. |
@emerick there's seems to be a bug on all the platforms where the report that was just submitted doesn't appear under Example of the issue that @GeetaSarvadnya is posting:
I'm guessing it's either:
|
@emerick without enabling it i can still see crash reports uploaded Not sure what data is uploaded to crash server with that setting being disabled by default |
@srirambv Yes, manual uploads are still allowed even when "crash reporting" is disabled. I think the option is specifically worded as "Automatically send usage statistics and crash reports to Brave", i.e. the "automatically" is the key part there. |
@kjozwiak OK, I see. I think you're correct and it's the second option that you list "when chrome://crashes is restored, the crash report is still being submitted, hence not appearing". Probably just down to timing as to whether you will see it that quickly. |
verified its a timing issue between uploading and display. With the automatic setting enabled, crash reports are shown instantly on |
@emerick @GeetaSarvadnya created #1299. However, it's not really a "blocker" or a high priority issue. Maybe it will fix itself once your backend performance improves? Either way, these are the two major issues remaining re: crash reports:
|
Went through verification using the following build under
Verification Passed on
|
@kjozwiak OK, I see, thanks for the details! I don't see any reason that Windows 7 in particular would be excluded, but I'll continue to dig around. |
Sounds good! Let me know if you need any help testing anything! The Win 7 issue has been around since the early days of b-l. Originally, reporting wasn't working on any platform. Win 7 & Linux where the only ones that weren't fixed. Seemed like the issue has followed us into b-c :( |
No description provided.
The text was updated successfully, but these errors were encountered: