@Biberkopf: Yep, K2/3/DX + framework start == 100% CPU for a while (depending on the size of the library), and since we need a good chunk of CPU time ourselves to process the image, and we're doing that at a very low priority, it can take a while for non-cached stuff

.