The extension takes a long time to respond when opening many tabs

120 views
Skip to first unread message

tanaka

unread,
Nov 18, 2024, 11:53:32 AM11/18/24
to AutoControl
This happens when i opened about 50 tabs, the CPU usage in Task Manager is about 60%. 
Then the response when switching tabs using mouse gestures became extremely slow. Usually it takes a second or two to successfully switch tabs, and sometimes, even though I used the mouse gesture, the arrow prompt on the screen took several seconds to appear. When switching tabs by hovering the mouse wheel over the title bar, the response is also very slow. Usually took a few seconds after scrolling to start switching, and then it takes several more seconds to complete the switch in the order of scrolling.
After encountering these issues, I have tried setting the native exe of AutoCtrl to Real time priority and configuring CPU affinity to avoid using CPU0 and CPU1, but it doesn't help much.

tanaka

unread,
Nov 18, 2024, 12:10:16 PM11/18/24
to AutoControl

https://youtu.be/grtWvzYNpCU screen record

The display window for mouse gesture was not successfully recorded, but it's clearly that the window switching actions are out of sync with my mouse movements

AutoControl support

unread,
Nov 19, 2024, 2:35:47 AM11/19/24
to AutoControl
A large amount of tabs cannot be the sole reason for 60% CPU usage. That's way too high. Chrome can easily keep 100 tabs open with minimal CPU usage.
A possible explanation for such a high usage is that one or more of those tabs are doing something computationally expensive.
You can find out which tabs are using the most CPU by pressing SHIFT+ESC (it opens the browser task manager).

Once you find the tabs that are using the most CPU, try closing them one by one and see if the gesture delay still happens.

Another possible cause is that one of your "RUN SCRIPT" actions is running a script that's slowing down AutoControl as a whole.
You can try disabling those script actions temporarily and then do an "Emergency repair" in order to stop any running script.
If the gesture delay disappears after that, then the culprit might indeed be one of your scripts.

Please let us know you findings.

tanaka

unread,
Nov 19, 2024, 5:09:33 AM11/19/24
to AutoControl
Yes, 60% CPU usage is with other software opened in the background. What I mean is that when I'm doing other tasks (like playing a game) that take up 50-60% of the CPU, the Chrome browser and web pages usually respond well. However, various operations and gestures of AutoControl are already significantly delayed. Even when I'm not running a game or other large tasks (CPU usage around 20%), many AutoControl gestures still experience partial delayed responses. The operation of scrolling with the mouse wheel on the Chrome title bar to switch tabs left and right is particularly laggy.
Emergency repair can interrupt gesture operations that have not responded for a long time, but it does not improve overall operation delay.

AutoControl support

unread,
Nov 19, 2024, 8:22:49 AM11/19/24
to AutoControl
Please try the following:
  1. Create a new browser profile
  2. Install AutoControl in it
  3. Create the 2 actions shown in the screenshot below
  4. Navigate to http://example.com and then click on the reload toolbar button with the middle mouse button 50 times (this will create 50 tabs)
  5. Now try turning the mouse wheel over the tab strip to check if there is a delay in the tab switching
image.png

tanaka

unread,
Nov 19, 2024, 9:07:44 PM11/19/24
to AutoControl
Yes, the issue persists, please take a look at my screen recording
https://youtu.be/wD1_DG9OeV0

AutoControl support

unread,
Nov 19, 2024, 10:34:13 PM11/19/24
to AutoControl
Thanks for your feedback. The latest beta version 2024.11.20 has a fix that may solve the issue.

Please try it and let us know if there's any improvement in the response time.

Message has been deleted

tanaka

unread,
Nov 20, 2024, 1:56:42 AM11/20/24
to AutoControl
I can confirm that this version's mouse gestures and scroll through tabs actions are much smoother!

AutoControl support

unread,
Nov 21, 2024, 4:53:24 AM11/21/24
to AutoControl
Glad to know the issue was solved. The fix will be added to the next official release. In the meantime you can keep using the beta version.
Thanks for your feedback.

Reply all
Reply to author
Forward
0 new messages