please find a way to solve the IE memory leak problems

New Functionality Requests
#1

There has got to be a way. Seems every component if created and closed, leaks memory in IE. Sometimes quite dramatically. Sometimes showing/hiding (as has been the suggested course of action) just doesn’t work due to the need to reload or call attachURL with a new URL. Even if I reuse a dhxWin but call attachURL again, the leak persists as if I created a brand new container in the first place.

This toolkit is so well built and so well thought out that it just baffles me that there isn’t a global solution in the toolkit for unloading used RAM regardless of the IE limitations. The problem can be so bad that I am forced (with great hesitation) to explore alternative options for UI toolkits.

#2

Which version of dhtmlx you are using?

#3

greetings. I am unsure how to obtain a specific build number. I use a single .js and .css build.

#4

There were memory leak related fixes in 2.6 version, which works much more stable than 2.5
So if you are using version 2.5 or early you can try to update to the most latest version - it must improve a situation.

#5

I thought I was at 2.6… again, I don’t see a build number referenced anywhere in my files.

I did find that the worst leaking offender could be mitigated by both reusing the dhxwin container AND updateing it like this:

myWin._frame.src = sMyUrl;

as opposed to updating it like this:

myWin.attachURL(sMyUrl)

edit: looking here:
dhtmlx.com/docs/products/dht … snew.shtml

I do not believe I yet have v2.6 based on those described features. I’ll try to get myself updated!