(In reply to Cieara Meador [:cmkm] from comment #11) > (In reply to Joachim Kuebart from comment #10) > > (In reply to Cieara Meador [:cmkm] from comment #9) > > > (In reply to Joachim Kuebart from comment #8) > > > Hi! Thanks for raising this concern. There's a related bug 1820171 for improving the performance of the tab manager you may want to watch. > > > > Thanks Cieara, that one isn't specifically about the new close buttons, but it sounds like the proposed solution with `content-visibility` would indeed also address this.. so I'll hope to be able to get and test this soon! ;-) > > Thanks for following up! If it's possible, it would also be super helpful if you'd be willing to share a profile. [You can find instructions to do this here](https://profiler.firefox.com/). Here's the profile with 114.0b9 which is *snappy*: https://share.firefox.dev/435bK87 Here's the profile with 115.0b9 which is *slow*: https://share.firefox.dev/44oT3gK The activities in both cases were: start profile, open tab manager, scroll around a little, close tab manager, stop profile.
Bug 1620199 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Cieara Meador [:cmkm] from comment #11) > (In reply to Joachim Kuebart from comment #10) > > (In reply to Cieara Meador [:cmkm] from comment #9) > > > (In reply to Joachim Kuebart from comment #8) > > > Hi! Thanks for raising this concern. There's a related bug 1820171 for improving the performance of the tab manager you may want to watch. > > > > Thanks Cieara, that one isn't specifically about the new close buttons, but it sounds like the proposed solution with `content-visibility` would indeed also address this.. so I'll hope to be able to get and test this soon! ;-) > > Thanks for following up! If it's possible, it would also be super helpful if you'd be willing to share a profile. [You can find instructions to do this here](https://profiler.firefox.com/). Here's the profile with 114.0b9 which is *snappy*: https://share.firefox.dev/435bK87 Here's the profile with 115.0b9 which is *slow*: https://share.firefox.dev/44oT3gK The activities in both cases were: start profile, open tab manager, scroll around a little, close tab manager, stop profile. At first glance, Graphics -> Other spikes from 34 (on 114.0b9) to 4823 (on 115.0b9) which seems to be the biggest concern.
(In reply to Cieara Meador [:cmkm] from comment #11) > (In reply to Joachim Kuebart from comment #10) > > (In reply to Cieara Meador [:cmkm] from comment #9) > > > (In reply to Joachim Kuebart from comment #8) > > > Hi! Thanks for raising this concern. There's a related bug 1820171 for improving the performance of the tab manager you may want to watch. > > > > Thanks Cieara, that one isn't specifically about the new close buttons, but it sounds like the proposed solution with `content-visibility` would indeed also address this.. so I'll hope to be able to get and test this soon! ;-) > > Thanks for following up! If it's possible, it would also be super helpful if you'd be willing to share a profile. [You can find instructions to do this here](https://profiler.firefox.com/). Here's the profile with 114.0b9 which is *snappy*: https://share.firefox.dev/435bK87 Here's the profile with 115.0b9 which is *slow*: https://share.firefox.dev/44oT3gK The activities in both cases were: start profile, open tab manager, scroll around a little, close tab manager, stop profile. At first glance, Graphics -> Other spikes from 941 (on 114.0b9) to 4823 (on 115.0b9) which seems to be the biggest concern.