First visit to www.rt.com yields "no trackers", simple reload yields many.

[DeriJames]

The image on the right shows that PB has detected no trackers (icon is green) but opening the same page in another firefox instance (or simply reloading in the first instance) causes PB to block a lot of trackers, see image on left, icon is amber.

Whilst the first instance is open, cpu activity is quite high, but no cpu activity occurs whilst the second instance is open. This behaviour is seen only the first time firefox is opened, if it is already running navigating to an rt.com page will block the trackers.

Is this behaviour expected?

[ghostwords]

Is your homepage set to rt.com, or is your Firefox set to reopen tabs from last time on start? This is then a duplicate of #1845.

[DeriJames]

Yes, I suspect you are correct (it is related), but it is not related to homepage definition. I suspect the underlying cause is because my typical use case is to click on a link in a KDE plasma RSS feed viewer, which results in an external call to "firefox ". So it looks like the delayed PB startup causes the trackers to be missed.

Many thanks for your reply.

[ghostwords]

OK, thanks for clarifying! Let's subscribe to #1845 for updates.