Thanks, just had a look. Don’t really see the issue, they don’t need to be stored in GPU RAM like textures for a game would be.
The version I’m running generates module thumbnails on first browser access, thereafter they’re displayed instantly, if I type filter for instance there is then zero delay in displaying everything tagged with filter. Now I’ve got used to that I find going back almost impossible, I frequently find myself looking for a module but by the time they’ve rendered I’ve forgotten what I was doing, don’t want to go into details but my brain can be awkward like that.
I’ve not looked at the browser source code, not back up to speed enough yet, however it appears that to create module thumbnails the ModuleWidget constructor is called for each module installed (I’ve code that exploits this, if *module is null, to display one of my modules differently in the browser to how it appears when running in the rack), it also appears that the official release does this every time the browser is invoked, whereas the version I’m running does it once only.