Created attachment 65183 [details] filesystem abuse produced by simply clicking on one application category in kde application menu Version: unspecified OS: Linux Just CLICKING on a menu category produces the attached result. On a busy machine, this can take minutes. There is NO NEED WHATSOEVER to issue thousands upon thousands of filesystem requests for ONE icon. See attached file. It's not funny at all -- it's just sad. And then people wonder why there's complaints that KDE is "slow". Reproducible: Always Steps to Reproduce: click on menu click on applications click on any category Actual Results: wait for five minutes twiddling my thumbs Expected Results: show me the damn list now!
there are reasons for those stats, and a reasonable filesystem should be able to deal with it. the next time you report a bug in a civil tone, i'll spend the time replying in greater detail and with more understanding.
There is no reason for blocking the UI while doing those stats. GNOME does not, for example -- it shows you the menu and the icons are populated after the fact if they are not already in RAM. There may be reason to perform some of these stats, but they should be done once, and then cached. This is the whole point of the icon cache. This has nothing to do with the filesystem, as this is a problem using any filesystem -- as soon as the icons you are trying to fetch are evicted from memory (dentry or page cache), the menu becomes slow to use, to the point that it takes minutes. Also, almost every KDE app does this when it needs icons -- it hammers the filesystem. Also, note how all icon sizes and icon categories are researched for each icon. Unnecessary. If you want to close the bug because it was "uncivilly" reported, that is fine. Just don't give me back a bunch of lies, Aaron.
*** This bug has been marked as a duplicate of bug 251217 ***