In my case (1) it is a complex clipping shape that gets created based on an
initial rectangle from which the code „subtracts“ a list of ellipses (2). The
clip is set on paths so that their rendering stops before they enter the
ellipses.
—Dirk
(1) https://twitter.com/dlemmermann/status/14740599
I tested this, and it seems to still not work quite right.
As far as I can see, it is not a memory leak, just slow performance when
subtracting many shapes from roughly the same location from another
shape. When the shapes are more spread out, it performs better.
I don't think it is a major
Noticed a recent tweet (1) about an older memory leak issue (2) and was
curious if with recent performance and memory changes if anyone can confirm
if this is still an issue or if it has been resolved as part of the recent
changes. There appears to be a test attached to the original issue.
Eric
