3 ms·
I don't think the package managers are at fault here and this would be much more easily fixed in Firefox itself by not touching the filesystem after Firefox sta
by account42 5y ago
I don't think the package managers are at fault here and this would be much more easily fixed in Firefox itself by not touching the filesystem after Firefox starts - resources are already bundled so you only need to keep a handle open (package managers don't change file contents but replace what the filename points to) and only fork instead of executing new processes (keep a pristine process running to fork from if you want).