Not just that, but in an earlier release code was shipped to set the pref for users who already had the file, so that anyone who already had one of these files would not observe any behavior regressions.
And yes, file I/O was the issue.
Yeah, I checked and it was automatically enabled for me, so no regression.
Re:Firefox 69.0 Released
by gregknicholson on Wednesday September 04, 2019 @02:27PM
(#20880031)
Thank you for doing this!
I can't claim credit for it; I hadn't even realized it had happened until I dug a little bit into the history while reading this thread. All I knew was that my userChrome.css was still working fine... ;)
Antivirus software does add a measurable delay to file operations sometimes, and each file is gonna be in its own sector so I could see them losing at least a few milliseconds there. Applying CSS does add overhead but the average user can't have that many rules in there so I suspect it's purely on the file i/o level.