(In reply to Diogo Freire from comment #29) > ...huh. Wasn't able to reproduce the bug. Just for the sake of doing (which I did months ago, and it still happened), I tried the troubleshooting mode on my profile, and the bug is gone? I feel It's either an add-on or a bad config on my profile. I guess ill need to check every add-on and see if a specific one is the culprit. There have been previous reports of this happening in Firefox profiles without any addons (see both bug 1750602 and [this webcompat bug](https://github.com/webcompat/web-bugs/issues/98416)), so it's unlikely that an add-on is the culprit. (Although if this is indeed timing-related, as the refresh-rate change suggests, it's possible that an add-on might change things sufficiently to suppress or reveal it.) Does testing with logging active affect whether the bug appears?
Bug 1763981 Comment 31 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 Diogo Freire from comment #29) > ...huh. Wasn't able to reproduce the bug. Just for the sake of doing (which I did months ago, and it still happened), I tried the troubleshooting mode on my profile, and the bug is gone? I feel It's either an add-on or a bad config on my profile. I guess ill need to check every add-on and see if a specific one is the culprit. There have been previous reports of this happening in Firefox profiles without any addons (see both bug 1750602 and [this webcompat bug](https://github.com/webcompat/web-bugs/issues/98416)), so it's unlikely that an add-on is the culprit. (Although if this is indeed timing-related, as the refresh-rate change suggests, it's possible that an add-on might alter the timing sufficiently to suppress or reveal it.) Does testing with logging active affect whether the bug appears?