Well, I think certainly related, but maybe not exactly the same.
You posted this 7 days ago, before extension version 2025.5.0 arrived in the browser stores (that was beginning of this week - maybe 4-5 days ago), and as I posted the GitHub issue there, that may be an “older bug”.
But now, with extension 2025.5.0, this seems to have gotten worse indeed (my personal impression/experience the last days)…