On 23 June 2016 at 16:19, J.F. Rick <self@je77.com> wrote:
Are .dmp files useful? If so, I can share those. I do still get crashes but they are far less since I only use one surface.
Another thing that is happening is that the form-based paints are sticking around though the form should have been collected. It seems like the way that paints are being handled is changing in Athens development. I tried upgrading but that broke things. Is there a way I can be at the bleeding edge and contribute back to the Athens development? I can't do anything on the C side but I can contribute on the Smalltalk side.
Unfortunately, i am not in the bussiness right now to help with your problem. And i cannot teach everyone how to handle problems with hanging pointers nor mentor people how to write code to prevent risk of their appearance in a first place. It is a common problem of every system with garbage collector under the hood.. now its time for Athens to face it. Oh well, one more, one less.. Such thing will keep popping up time to time around the place, unless people start to think before coding :)
I guess, someone who made those changes could help you better.
Cheers,
Jeff
On Thu, Jun 23, 2016 at 7:11 AM Igor Stasenko <siguctua@gmail.com> wrote:
On 18 June 2016 at 19:36, 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?
follow the pointers and look for the culprit, that holding it and not releasing. That's all i can advice.
Cheers,
Jeff
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.