On Jun 22, 2016, at 1:18 PM, J.F. Rick <self@je77.com> wrote:

Here's some more information on this: When I was having this issue, Pharo was pretty unstable. It would crash regularly when using AthensCairoSurface. It would also sometimes have weird visual artifacts. I'm not sure what these were but it almost looked like the bits were shifted so that rgb turned into gbr or something. Anyway, I've gone ahead and dumped that image, loaded all the same code, and started making sure that I don't save the image when testing the code. I haven't had a crash since. Perhaps that gives a clue about what was going on.

Cheers,

Jeff

PS This is on the Ubuntu16 and Pharo5.

On Sat, Jun 18, 2016 at 12:36 PM J.F. Rick <self@je77.com> wrote:

I'm using Athens rendering for my multi-touch applications on Pharo5. As part of that, I create a surface:

surface := AthensCairoSurface extent: bounds extent asIntegerPoint.

Though the object creating that surface is deleted, the surface sticks around. So, each time I run the app, I get another instance of AthensCairoSurface hanging around. That means all the forms stick around as well. So my image can quickly grow towards the 1GB size.

 Is there anything I can do about that? Can I manually get the surface to delete itself?

Cheers,

Jeff