Delay after new Tab in Tabgroup with hiding

[TabNoc]

When a new Tab is opened (via button or ctrl + T) and "only show tabs of the current container" is active and the current tab is in a TabGroup, then the new Tab will be opend in the default TabGroup. The visible Tabs will be switched to the default group, while the correct TabGroup (from the old Tab) will be applied to the Tab, and visibility is changing back to the Tabgroup.
With many tabs to show/hide this process takes some time and is anoying, maybe add a timer to apply switch of visible TabGroup after no change in 100ms, or so.

[kesselborn]

hey: thanks for the issue and sorry for the long delay.
Hm ... the way this works is that Firefox always opens a new tab in the default group but conex intercepts this, closes the opened tab and reopens it in the current container.
I am not sure, if I can intercept this before it switches to the default group on your system (it does not happen on my system + I never got this feedback from somebody else).

Could you quickly provide the following info about your setup please:

• your os
• your Firefox version
• the conex version you are using

Cheers

[TabNoc]

Hi Daniel, I have tried it on 2 different systems (Win 7 [FF 60.0b12] and Win 10 [FF 60.0b10/FF60.0b13]) both running Conex 0.7.5. I have to admit that on both systems I have a huge amount of Tabs (Win 10 about 1600/Win 7 about 500). It happens also, when Firefox get a link to open from external.

[kesselborn]

thanks for the reply and sorry for the delay. I will probably have to create a profile with many open tabs to recreate the problem :/

[maverick74]

I was looking to find if this bug was already submitted.

This is something i've always experienced from the very beginning and like @mnpingpong says it's very annoying!!!

About my system: i also always have many tabs open while working (in this moment i have 81, but it does reach more than 100-150 easily). Still even with few tabs i can experience this lag.

I'm on openSUSE Tumbleweed
with an Intel dual core and 8Gb of RAM,
i'm using Firefox 61
with Conex 0.7.9.

The same thing happens on my laptop (win10), on my main computer (Linux) and in another workstation (Win10) where Conex is used, so i believe it's not OS related or even Firefox related

@kesselborn is there any news in this problem?

[terrizgit]

I just tried this, and I can see it happening - it's very brief, but I only have ~40 tabs open - but I can see how with many tabs it could be annoying!

Firefox 60.0.2
Mas OS X 10.13.5
Conex 0.7.9
2.4GHz Intel processor
16G memory

[maverick74]

@kesselborn were you able to recreate the issue?
(i'm about to jump over my computer, with both feet - repeatedly - over this thing :p)

if i can provide any help just say so :)

[kesselborn]

I am sorry, but I can't fix it. It seems to be a performance problem. What you see is how Conex works (unfortunately: has to work): it intercepts opening a new tab, grabs the url, closes the new tab and opens the url in a new container. What happens in your cases is, that the process is so slow, that you see it.
I can't see it here (even with 100s of open tabs) :(

[maverick74]

ok... i understand!

Thank you, anyway :)