Forum Discussion
- I have two Macs (iMac 2020 and MBP14).
- Usually, I use iMac 2020 for all my work-related things and there are more than 100 tabs opened. As I commented earlier in this thread, I have been suffered from using cmd+\ on iMac and it has been failed since day 1 of 1P8 use on me (takes more than 30 secs for cmd+\ ).
With MBP14, I only check emails and read papers so there are always less than 10 tabs opened. And NO ISSUE at all with cmd-\ . It works within a second.
So, I thought the problem in this thread could be related to the number of opened tabs in Chrome and decided to do some tests.
Here are the test results that I've done with 1P8 (w/ Chrome extension) on my MBP14 to see/replicate this performance issue on different number of opened tabs.
1 tab (facebook login page): cmd+\ takes less than a second
open 20 more dummy tabs (Youtube) and trying to login at the first tab (FB): cmd+\ takes 6-7 seconds
open 20 more (total 41) tabs: cmd+\ takes arounds 15 seconds
open 20 more (total 61) tabs: cmd+\ takes more than 30 seconds, showing spinning wheels, chrome does not respond for a while..., finally fill the pw, but takes 10 or more seconds to successfully login to FB, etc.
Now, I think the problem might be related to the number of opened tabs in Chrome and maybe the chrome extension iterates all the tabs to do some tasks and that makes the Autofill slow.
I hope my experience could help to debug this issue and get resolved near in the future.