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

Crash report isn't listed immediately after sending the report manually #1299

Open
GeetaSarvadnya opened this issue Sep 26, 2018 · 1 comment
Labels
bug priority/P5 Not scheduled. Don't anticipate work on this any time soon. QA/Yes

Comments

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Sep 26, 2018

Description

Crash report isn't listed immediately after sending the report manually

Steps to Reproduce

  1. Launch b-c with clean profile from CLI
  2. Enter chrome://crash and crash a tab
  3. Enter chrome://crashes in a new tab and see the crash
  4. Click on "send" and restart the browser
  5. Once restarted, notice that chrome://crashes is blank
  6. Refresh chrome://crashes
  7. Notice that the report is appeared and submitted
  8. Check stats.brave and check the crash report

Actual result:

Crash report isn't listed immediately after sending the report manually
crash report issue

Expected result:

Crash reports should be generated immediately after browser restart

Reproduces how often

Always

Brave version (chrome://version info)

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

Reproducible on current release:

NA

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? - NA
  • Is the issue reproducible on the latest version of Chrome? - NA

Additional Information

@kjozwiak @LaurenWags @srirambv @btlechowski

@kjozwiak
Copy link
Member

I'm guessing it's because of either:

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

Probably the the later which explains why sometime it works and sometimes you have to refresh the tab.

@rebron rebron added the priority/P5 Not scheduled. Don't anticipate work on this any time soon. label Sep 28, 2018
@rebron rebron removed this from the 1.x Backlog milestone Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug priority/P5 Not scheduled. Don't anticipate work on this any time soon. QA/Yes
Projects
Status: P5 Backlog / waiting upstream
Development

No branches or pull requests

3 participants