memory leak on zoom in/out

Post by **pincherhgz** » Thu Nov 05, 2015 1:28 pm

doing the profiling for our app we are facing the problem that we have a memory leak (objects not collected by the GC) when using the zoomToLevel method.
You can reproduce that using your zoom example. The snapshot analysis after pressing zoom in and out shows this (see attached picture)

Post by **Maxim Gorkovsky** » Fri Nov 06, 2015 11:03 am

Hello.
Thank you for report, I opened a ticket to investigate this: https://www.assembla.com/spaces/bryntum/tickets/2386
Does this have major impact on your application?

Post by **pincherhgz** » Fri Nov 06, 2015 11:06 am

Hi,
we can live with that for the next 2 months but need it solved to allow us releasing our product within Q1/2016

Post by **pincherhgz** » Sun Nov 08, 2015 8:17 pm

we checked again during the weekend and an part of our application (where we are showing on huge monitors permanently changing situations that need the zoom call) is running already after a day out of memory, so we need more urgent help.
thanks in advance

Post by **mats** » Sun Nov 08, 2015 8:26 pm

Thanks for the update, we'll try to do a preliminary analysis this coming week. Please keep us posted on your findings

Post by **mats** » Tue Nov 10, 2015 10:27 am

Could not find anything substantial here. After doing 100s of zoom in/out I see memory go up by about 1MB which could be anything (Sencha Touch internals or browser not having done all the GC yet). Could you share some more information on why you think it's a leak still?

Post by **mats** » Tue Nov 10, 2015 12:10 pm

Found two other leaks that has now been fixed, please re-test in next nightly build.

Post by **pincherhgz** » Tue Nov 10, 2015 12:12 pm

great, we'll do so

Post by **mats** » Wed Nov 11, 2015 4:24 pm

any results?

Post by **pincherhgz** » Wed Nov 11, 2015 4:59 pm

it's much better now, we continue to check

Support Forum

Bryntum Support Forums

memory leak on zoom in/out