You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TreeStyleTabs seems to busy-wait/busy-poll stuff all the time.
Steps to see the situation
Have a browsing session with, in my case, 644 tabs over 35 windows; otherwise completely idle (most of those tabs are 'discarded', see AutoTabDiscard)
In about:processes, see "Extensions" taking up nearly 100% of one core (i7-6700HQ)
Click on the conveniently located "Profile all threads of this process for 5 seconds" button of the Extensions process
In the profile result, see updateTimeoutTimer in moz-extension://6efa3d93-bed2-4dff-a92a-064725d94b45/common/sidebar-connection.js:165:31 as the 'culprit'
Expected result
Idle CPU usage of below 30% ideally.
Actual (present) result
Idle CPU usage of 70% - 115% pretty much all the time.
Additional remarks
I'd be happy to know about a tunable where I could trade off this CPU usage against how quickly TST reacts to new tabs or such (which, by the way, already is noticeably slow for me - but if that is 'because' or 'despite' of this issue, I cannot say).
Environment
Platform (OS): Gentoo amd64
Version of Firefox: LibreWolf 118.0.1-1
Version (or revision) of Tree Style Tab: 3.9.17
The text was updated successfully, but these errors were encountered:
Could you try larger value for heartbeatInterval, for example 10000 ? The insternaloption is configurable via TST otpsions => Development => All Configs.
This issue has been labeled as "stale" due to no response by the reporter within 1 month (and 7 days after last commented by someone). And it will be closed automatically 14 days later if not responded.
Abstract
TreeStyleTabs seems to busy-wait/busy-poll stuff all the time.
Steps to see the situation
about:processes
, see "Extensions" taking up nearly 100% of one core (i7-6700HQ)updateTimeoutTimer
inmoz-extension://6efa3d93-bed2-4dff-a92a-064725d94b45/common/sidebar-connection.js:165:31
as the 'culprit'Expected result
Idle CPU usage of below 30% ideally.
Actual (present) result
Idle CPU usage of 70% - 115% pretty much all the time.
Additional remarks
I'd be happy to know about a tunable where I could trade off this CPU usage against how quickly TST reacts to new tabs or such (which, by the way, already is noticeably slow for me - but if that is 'because' or 'despite' of this issue, I cannot say).
Environment
The text was updated successfully, but these errors were encountered: