search

svenmeier / wicket-dnd

Wicket drag-and-drop
20 stars 14 forks source link

Ajax-replacing a element that is a DnD DragSource seems to leak memory? #22

Open d2a-raudenaerde opened 6 years ago

d2a-raudenaerde commented 6 years ago

Hi Sven,

I'm analysing the performance of our application, and it seems there is memory leaking. When trying to analyse in chrome developer tools what was going on, it seemed there was some leakage related to element that where marked as DragSource. I took two heap-snapshots. One before ajax-replacing a Component used as DragSource, and one after. There is a lot going on, but there is extra heap afterwards. The I removed the DragSource and tried again, resulting in a lot less extra memory. I'm not up-to-par yet analysing heap dumps in chrome, but maybe you an shed a light on what would 'leak' if a Component is replace by Ajax?

svenmeier commented 6 years ago

Hi Rob,

does this happen regardless of any DnD? I.e. is it sufficient to replace markup containing a DragSource, or do you have to drag something before?

Sven

svenmeier commented 6 years ago

I've tried with wicket-dnd-examples: Each click on one of the checkboxes updates markup with a DragSource and DropTarget.

With Chrome's memory tools I didn't notice any leaks.