Bugzilla

I've been trying to track down what is happening today. My findings so far
1. Nothing changed in the app update client after 66.0b10 so an app update client change is extremely unlikely.
2. The omni.ja that contains the css file (svg.css) is updated after firefox.exe and before xul.dll both of which have the correct version. If this were due to an update failure (e.g. low disk space, updater crash, etc.) that failed to rollback to the original state then the file versions would be incorrect.

I did notice that the compatibility.ini file is located in the Windows roaming profile and the startup cache is located in the Windows local profile. I don't know the startup cache code well enough to know for certain but it seems that if a client with a roaming profile updated and then used that roaming profile on another system that had already been updated the profile's compatibility.ini would report it as compatible but the users startup cache in the Windows local profile would be for the old version and not be purged.

I'm looking into what could be added to the crash reports that might help narrow this down.

I've been trying to track down what is happening today. My findings so far
1. Nothing changed in the app update client after 66.0b10 so an app update client change is extremely unlikely.
2. The omni.ja that contains the css file (svg.css) is updated after firefox.exe and before xul.dll both of which have the correct version. If this were due to an update failure (e.g. low disk space, updater crash, etc.) that failed to rollback to the original state then the file versions would be different.

I did notice that the compatibility.ini file is located in the Windows roaming profile and the startup cache is located in the Windows local profile. I don't know the startup cache code well enough to know for certain but it seems that if a client with a roaming profile updated and then used that roaming profile on another system that had already been updated the profile's compatibility.ini would report it as compatible but the users startup cache in the Windows local profile would be for the old version and not be purged.

I'm looking into what could be added to the crash reports that might help narrow this down.