This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 970
UI becomes unresponsive when rapidly creating tabs via CTRL + T
#10749
Labels
bug
feature/newtab
fixed-with-brave-core
This issue will automatically resolved with the replacement of Muon with Brave Core.
priority/P4
Minor loss of function. Workaround usually present.
release-notes/include
wontfix
Comments
bbondy
added a commit
that referenced
this issue
Aug 31, 2017
Fix #10749 I don't think I can add a test for this since it's so unfrequent but it will go away once we get rid of frame state
bbondy
added a commit
that referenced
this issue
Aug 31, 2017
Fix #10749 I don't think I can add a test for this since it's so unfrequent but it will go away once we get rid of frame state
bbondy
added a commit
that referenced
this issue
Aug 31, 2017
Fix #10749 I don't think I can add a test for this since it's so unfrequent but it will go away once we get rid of frame state
App is quite slow when opening a lot of tabs on Windows. CPU usage spikes a lot while loading pages on all tabs. |
@kjozwiak what is the issue not fixed here? |
+1 from me (#10866) |
From the screenshot by @kjozwiak, this is where it's crashing at (state is null/undefined): browser-laptop/js/stores/windowStore.js Line 131 in b47daf7
This is fired when processing the |
bbondy
added a commit
that referenced
this issue
Oct 6, 2017
bbondy
added a commit
that referenced
this issue
Oct 6, 2017
bbondy
added a commit
that referenced
this issue
Oct 6, 2017
bbondy
added a commit
that referenced
this issue
Oct 6, 2017
@kjozwiak , what software did you use to record the video / image / animation of the Brave tabs above? |
We're finally going to get rid of this with |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
feature/newtab
fixed-with-brave-core
This issue will automatically resolved with the replacement of Muon with Brave Core.
priority/P4
Minor loss of function. Workaround usually present.
release-notes/include
wontfix
- Did you search for similar issues before submitting this one?
Yes
- Describe the issue you encountered:
When rapidly opening a bunch of tabs via "CTRL + T", the Brave UI becomes completely unresponsive after opening 6-15 tabs.
- Platform (Win7, 8, 10? macOS? Linux distro?):
Win 10 x64 - Reproduced
macOS 10.12.6 x64 - Reproduced
- Brave Version (revision SHA):
- Steps to reproduce:
CTRL + T
- Actual result:
The entire Brave UI becomes unresponsive
- Expected result:
The Brave UI shouldn't become unresponsive when rapidly opening tabs via
CTRL + T
- Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes
- Is this an issue in the currently released version?
No
- Can this issue be consistently reproduced?
Yes, using the above STR, the issue is 100% reproducible
- Screenshot if needed:
The text was updated successfully, but these errors were encountered: