Skip to content

crash when closing multiple inactive tabs with same address #1488

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

Closed
LaurenWags opened this issue Oct 10, 2018 · 3 comments
Closed

crash when closing multiple inactive tabs with same address #1488

LaurenWags opened this issue Oct 10, 2018 · 3 comments

Comments

@LaurenWags
Copy link
Member

LaurenWags commented Oct 10, 2018

Description

With Rewards enabled, if have two YT tabs open and they are both inactive, when I close the second one Brave crashes. I've only been able to reproduce this with Rewards enabled and YouTube tabs, other sites have not reproduced this crash.

Steps to Reproduce

  1. Clean profile
  2. Enable rewards (leave tab open)
  3. Open new tab, navigate to YT video (I used https://www.youtube.com/watch?v=dVMYC4s341o)
  4. Play video for a bit (20-40s is sufficient)
  5. Pause video
  6. Go back to chrome://rewards tab --> See video creator listed in auto contribute panel
  7. Click on video creator link —> New tab opens with expected page
  8. Go back to paused video tab
  9. Click on creator name, then click on Videos at top --> You now have two pages open with the same link
  10. Open a new tab
  11. Make Brave inactive for a few minutes (work in slack, another app, etc)
  12. Make Brave active again.
  13. While on the new tab, click on x to close one of the video tabs
  14. Click on x to close second video tab

Actual result:

Brave Crashes

Expected result:

No crash, tab should close

Reproduces how often:

easily

Brave version (chrome://version info)

Brave 0.55.12 Chromium: 70.0.3538.45 (Official Build) beta(64-bit)
Revision cbdc32e4334458954e9def214d7e5fa1ca1960eb-refs/branch-heads/3538@{#830}
OS Mac OS X

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds? yes
  • Does it reproduce on browser-laptop? no

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? n/a
  • Is the issue reproducible on the latest version of Chrome? n/a

Additional Information

cc @brave/legacy_qa to check on other platforms
cc @NejcZdovc since this is a crash but it's an unusual series of steps. I've only been able to repro with rewards enabled.

@kjozwiak
Copy link
Member

kjozwiak commented Oct 11, 2018

Adding this into the 1.0 (0.56.x) milestone as we should flush out as many crashes as we can before launching 1.0. Crashing is never good!

@bbondy
Copy link
Member

bbondy commented Oct 11, 2018

Dupe of
#1494

I think this crash will appear fairly often in various different cases, so probably wait for next build for more.

@LaurenWags
Copy link
Member Author

LaurenWags commented Oct 15, 2018

Verified passed with

Brave 0.55.14 Chromium: 70.0.3538.54 (Official Build) beta(64-bit)
Revision 4f8e578b6680574714e9ed3bb9f02922b4dde40d-refs/branch-heads/3538@{#937}
OS Mac OS X
  • Verified STR from description several times and no crash was observed.

Verification Passed on

Brave 0.55.14 Chromium: 70.0.3538.54 (Official Build) beta(64-bit)
Revision 4f8e578b6680574714e9ed3bb9f02922b4dde40d-refs/branch-heads/3538@{#937}
OS Linux
  • Verified steps mentioned in issue

Verification passed on

Brave 0.55.14 Chromium: 70.0.3538.54 (Official Build) beta(64-bit)
Revision 4f8e578b6680574714e9ed3bb9f02922b4dde40d-refs/branch-heads/3538@{#937}
OS Windows 7

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

5 participants