Skip to content
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

Closed
bbondy opened this issue Jun 6, 2018 · 21 comments
Closed

Create a new crash reporting endpoint #285

bbondy opened this issue Jun 6, 2018 · 21 comments

Comments

@bbondy
Copy link
Member

bbondy commented Jun 6, 2018

No description provided.

@bbondy
Copy link
Member Author

bbondy commented Jun 25, 2018

We'll just be re-using https://laptop-updates.brave.com/1/crashes for now.
Can this be closed @aekeus or is there anything else to do here?

@aekeus
Copy link
Member

aekeus commented Jun 25, 2018

Yes, we will need to inspect the platform from the crash and send it to a different queue. cc @KarateCowboy

@emerick
Copy link
Contributor

emerick commented Jun 26, 2018

Sounds like we'll use the endpoint 1/bc-crashes for brave-core.

@aekeus
Copy link
Member

aekeus commented Jul 26, 2018

Implemented by brave/vault-updater@4cf8e50

@aekeus aekeus closed this as completed Jul 26, 2018
@bbondy bbondy assigned aekeus and unassigned KarateCowboy Aug 18, 2018
@bbondy bbondy added the QA/Yes label Aug 18, 2018
@bbondy
Copy link
Member Author

bbondy commented Aug 18, 2018

QA notes: Just make sure you can send a crash from about:crashes and that you can search for the ID.

@srirambv
Copy link
Contributor

Linux Crash doesn't list in chrome://crashes. Navigating to chrome://crash shows this error message
image

@bbondy
Copy link
Member Author

bbondy commented Sep 24, 2018

@srirambv pls post an issue for the 1.x backlog for ^

@btlechowski
Copy link

Sending crash reports does not work on Win7: #1188

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Sep 26, 2018

On windows 10 also, crash reports are not getting generated.
crash reports doesn t list under chrome crashes- win10

@emerick
Copy link
Contributor

emerick commented Sep 26, 2018

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

@kjozwiak
Copy link
Member

kjozwiak commented Sep 26, 2018

@emerick there's seems to be a bug on all the platforms where the report that was just submitted doesn't appear under chrome://crashes when the tab is restored after a restart. @GeetaSarvadnya is creating a new bug. Reports are being submitted though 👍

Example of the issue that @GeetaSarvadnya is posting:

  • visit chrome://crash in a new profile
  • open a new tab, visit chrome://crashes and click on Send
  • Restart the browser and the restored chrome://crashes window won't display the recent crash
  • refresh the same tab, and you'll notice that the crash will appear as submitted as expected

I'm guessing it's either:

  • chrome://crashes isn't correctly refreshed when it's the active tab and is restored
  • when chrome://crashes is restored, the crash report is still being submitted, hence not appearing

@srirambv
Copy link
Contributor

srirambv commented Sep 26, 2018

@emerick without enabling it i can still see crash reports uploaded
crash

Not sure what data is uploaded to crash server with that setting being disabled by default

@emerick
Copy link
Contributor

emerick commented Sep 26, 2018

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

@emerick
Copy link
Contributor

emerick commented Sep 26, 2018

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

@srirambv
Copy link
Contributor

verified its a timing issue between uploading and display. With the automatic setting enabled, crash reports are shown instantly on chrome://crashes and uploaded as well.

@kjozwiak
Copy link
Member

kjozwiak commented Sep 26, 2018

@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:

@emerick
Copy link
Contributor

emerick commented Sep 26, 2018

@kjozwiak Is #1188 not the same chrome://settings/ problem?

@kjozwiak
Copy link
Member

kjozwiak commented Sep 26, 2018

Went through verification using the following build under macOS 10.13.6 x64 - PASSED

Brave 0.55.6 Chromium: 70.0.3538.16 (Official Build) dev (64-bit)
Revision 16ed95b41bb05e565b11fb66ac33c660b721f778-refs/branch-heads/3538@{#306}
OS Mac OS X

Verification Passed on

Brave 0.55.6 Chromium: 70.0.3538.16 (Official Build) dev (64-bit)
Revision 16ed95b41bb05e565b11fb66ac33c660b721f778-refs/branch-heads/3538@{#306}
OS Windows 10

@srirambv srirambv removed the QA/Yes label Sep 26, 2018
@kjozwiak
Copy link
Member

@kjozwiak Is #1188 not the same chrome://settings/ problem?

Nope, it doesn't work on Win 7 in general. Both manual submission and automatic via Automatically send crash reports to Brave doesn't work. Added more information into #1188.

@emerick
Copy link
Contributor

emerick commented Sep 26, 2018

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

@kjozwiak
Copy link
Member

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 :(

@bbondy bbondy added the QA/Yes label Sep 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants