Memory leak after dhtmlX window closed?

Hello there,

We are using the following code to pop up and close the window:

  var dhxWins;
  popupForm: function(...) {
	  dhxWins = new dhtmlXWindows();
	  win = dhxWins.createWindow(winId, 5, 190, 750, 450);
	  win.attachEvent("onClose", onPopupClose);
        	url: url,
        	load: function(response, ioArgs){
        		var tag = document.createElement('div');
 = "div" + formId;
        		tag.innerHTML= response;
        		win.attachObject("div" + formId);
        	error: function(response, ioArgs) {
        	        ... // error handling
  onPopupClose: function(win) {
         ... // internal cleanup

Our code appears to follow the standard usage of dhtmlx straight out of the tutorials. What we observe is a sizable memory which gets bigger and bigger every time we open and close the dhtmlx window. From other posts here, it appear that in dhtmlx version 2.5, this was a known problem, but we are using version 3.0. Is there still a known memory leak in version 3.0?

We diagnosed the leak using the tool called sIEve, which detects “orphan” elements referring to dhtmlx controls. I’ve attached the sIEve output which flags a number of elements of the dhtmlx_wins_btns_button class as orphaned.

Perhaps we are missing something obvious in the code? Thanks.

update will available in future release. if you have enterprice license please login to and apply for hotfix