I don't have enough evidence either way, but the signs point to no since the applications that crash are not ones that use form-based paints. I assume they wouldn't be affected by the flush. We did have one crash on a form-based one where it crashed after running for 10 hours. My guess is that one ran out of memory. That crash is probably resolved. But, I'll keep everybody informed as I work more on it.
Cheers, Jeff On Thu, Jul 7, 2016 at 3:28 AM Alexandre Bergel <[email protected]> wrote: > Jeff, does this flush reduces the amount of crash you are experiencing? > > Alexandre > > > On Jul 6, 2016, at 9:01 PM, J.F. Rick <[email protected]> wrote: > > > > Nicolai, > > > > THANKS! That worked. I no longer have any AthensCairoCanvas hanging > around after executing "CairoBackendCache flush". > > > > Cheers, > > > > Jeff > > > > On Sun, Jul 3, 2016 at 11:58 AM Nicolai Hess <[email protected]> > wrote: > > Hi Jeff, > > > > if you use forms to paint on an AthensCairoCanvas, they are cached in > the CairoBackendCache, > > can you try to flush that cache whith > > CairoBackendCache flush. > > > > > > 2016-06-18 18:36 GMT+02:00 J.F. Rick <[email protected]>: > > 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 > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >
