bulia byak wrote:
... This problem became much worse after implementing Gaussian blur, because rendering blurred objects at high zooms may require a pixel buffer much bigger than the visible canvas...
This seems odd, why would you ever need a pixel buffer *much* larger than the visible canvas? Is it because the entire object has to be rendered? If so, can something be done about that? (might also speed things up)
The "100Mb" magic number was chosen so that to prevent too large allocations which, even if they succeed, bog the system down to an almost unusable state. I realize it's far from perfect, but at least it's a solution which kinda works for a "typical" system with at least 256Mb memory. Any suggestions on how to better handle this are welcome.
For rendering purposes this seems okay, but is this also enabled when exporting? Personally I wouldn't mind waiting a long time when exporting (not that I am likely to actually have documents that would approach this limit, but still), and I've got 1GB of memory, so I would rather see Inkscape just try to do the best it can.
And, assuming it's not possible to remedy the situation, when rendering it might be a good idea to create some kind of visual indication of having skipped some part (so the user isn't left wondering what the hell happened and possibly even tries to apply an effect twice for example).