-
Notifications
You must be signed in to change notification settings - Fork 2.5k
When using vertical tabs, pinning a tab that is part of a group crashes the browser - follow up to #40201 #40365
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
Comments
cc: @sangwoo108 |
@bsclifton we need someone to pick this one up |
Checking the PR brave/brave-core#25406 |
Found more concrete STR. |
This is upstream issue. Filed https://issues.chromium.org/issues/371112521. |
Trying to fix with https://chromium-review.googlesource.com/c/chromium/src/+/5919961 |
Requires 1.71.113 or higher for verification 👍🏻 @brave/qa-team can see concrete STR via brave/brave-core#25983 (comment) and my verification notes from brave/brave-core#25983 (comment) for guidance when testing. |
Verification INPROGRESS on
Reproduced the issue on |
Description
Found while testing #40201 for uplift
Crash when attempting to pin a tab in a tab group still happens sometimes. When a tab group has 1-2 tabs, I couldn't reproduce the crash with
1.70.57
, but it easily reproduced with1.70.56
. However, once my tab group had more tabs (3-4), then the below STR relatively reliably reproduced a crash for me. Not 100%, but the crash was fairly consistent.Steps to reproduce
Note, in step 7 I've also tried pinning a different tab in the group, sometimes that caused a crash, sometimes not
Actual result
browser crashes
Expected result
browser should not crash
Reproduces how often
Easily reproduced
Brave version (brave://version info)
Channel information
Reproducibility
Miscellaneous information
Crash ID:
ffc50300-15c1-690c-0000-000000000000
Call Stack
Crash ID:
b1c70300-15c1-690c-0000-000000000000
Call Stack
The text was updated successfully, but these errors were encountered: