Allowing to cache many large FilterImages can cause a memory jetsam. We tried to solve this problem by not applying the filter if the number of filter effects exceeds a certain maximum (currently it is 100).

Instead we should look at the estimated total memory size if we cache all the results. But even if we decide to no cache the result because their memory will exceed a certain maximum (say 100 MB), we should still apply the SVGFilter without caching the results. This may be very inefficient especially with cases where a result FilterImage is used multiple times. Caching it saves time, but we have to regenerate it every time we need it. Of course this is better than not displaying anything for the filtered image.