Description of problem: I've noticed there is something very strange about gtk-update-icon-cache/-3.0 When I look into: /usr/share/icons/oxygen I could see - there is 38MB if icons (quite frankly I don't get the idea why all size are distributed when it seems to be clearly visible, that smaller version are just downsized icons - thus could be probably downsized at the moment they are really needed - lazy eval) The bigger problem I could see - is 133MB icon-theme.cache. (gnome 17MB data, 51MB cache; crystalsvg 14MB data, 24MB cache) I don't get the idea how is to possible to build cache file 3 times bigger then original data set - moreover most probably majority of this cached data will never be used - so the only purpose is probably to eat some disk space? (it's still not that cheap on SSD...) What is actually the benefit of this cache file - is it measurable - could I disable it and use non-cached version to save like 1/4GB at least through some config option ? Version-Release number of selected component (if applicable): gtk3-2.90.5-5.fc15.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
this needs to be discussed upstream; in any case, the short answer is that the icon cache contains uncompressed data that can be directly mmapped and shared between all apps, the on-disk files contain compressed data