Incorrect rendering and 16 exabyte memory usage.

[Polarina]

1. Open Inkscape.
2. Effects -> Render -> Random Tree (Initial size: 100.0, Minimum size: 1.0).
3. Scale the resulting tree to fit the current A4 page. No need for precision here.
4. Effects -> Modify Path -> Fractalize (Subdivisions: 4, Smoothness: 4.0).
5. <Not always reproducible> Help -> About Memory -> Recalculate.

[pbhj (pbhj)]

You have 16 exabytes of RAM?

[Polarina (gabrielp-simnet)]

Of course I don't have 16 exabytes of RAM - Inkscape reports, incorrectly, its usage as such.

[Antonio Roberts (hellocatfood)]

I can't even get the Fractalize script to complete, let alone analyze the RAM usage

[nightrow (jb-benoit)]

Can you please try again on recent SVN build, so we can this closed or confirmed ?

[Antonio Roberts (hellocatfood)]

I tried again on inkscape21287-0905051558.7z and got a runtime error on step 4. The window goes white so I can't see the exact error message

[Alvin Penner (apenner)]

memory usage of 16 exabyte confirmed on Windows XP, build 21287.
I will mark this as Confirmed, but I would recommend that someone also mark it as "Will Not Fix".
  The point is that the complexity of this task will almost certainly grow exponentially as the ratio of the max to the min size in step 2, and there is no great advantage in using a ratio of 100 to 1 in step 2. For example, I got a very interesting tree using the values of 100 and 5 in step 2, tree attached.

[Pablo Trabajos (pajarico)]

Does the rendering problem depend on zoom level? It looks like a duplicate of bug 166867.

[su_v (suv-lp)]

the first bug that I could finally find in a series of reports related to zoom, fill color and stroke width rendering errors is bug #166112. I'd even link bug #166867 back to it (after having found 166112 ;-)

[su_v (suv-lp)]

Another series of renderer bugs seems related to single paths with huge numbers of nodes, a recent one is bug #428415 “Portions of path not drawn on screen or exported", but I have seen several earlier ones as well.

OTOH this bug here is about the performance of the python script that obviously fails when calculating several recursions of the fractalize script. To me it seems solely a performance limit of the script extension implementation, maybe even outside of Inkscape due to the fact that python is a script interpreter not running binary code optimized for special tasks.