Guriddo » Topic: memory not released after window close()

memory not released after window close()

Guriddo
memory not released after window close()

This topic has 6 replies, 2 voices, and was last updated 16 years, 5 months ago by dirk.

Creator

Topic
January 21, 2010 at 3:23 pm #75278

dirk
Participant

hello,

I have 1 main page that uses a window.open() to another pages, containing a JQGRid (which works perfect by the way).

When Imonitor the memory consumption, I see then when openeing this 2nd page approx 2MB is added, but when closing it, only a portion of that is returned. Another strange thing is that this only happens with IE7, so not (or not so obvious anyhow) on IE8, firefox 3.5 and IE6.

I have been trying to localize the issue, but without any success.

any ideas where to look?

thanks

dirk
Creator

Topic

Viewing 6 replies - 1 through 6 (of 6 total)

Author

Replies
January 24, 2010 at 6:56 pm #92312

tony
Keymaster

Hello,

Thanks for the investigation.

I think that the problem is in the IE JS garbage collector. We have created a special unload functon for IE browsers, but since you use

window.open, then the browser should have decision what to clear after the windows is closed.

Best Regards

Tony

January 27, 2010 at 11:03 am #92377

dirk
Participant

hello,

I have been investigating further, but the same issue arise with firefox (3.5) as well, only in a smaller way.

Do you have any idea on how to solve this. I did a 'refresh' of the same page, lest say 50 times, and the memory did not go up. only when you close and open the window via window.open() it goes up very very quick. Is there a way to get official support for this? I'm evaluating your product for purchasing, after a series of test the memory is the only one left open.

do you have some pointers or areas to look into to see what is causing this? (i have already tried the new jquery 1.4, but the issue is still the same). so in this case it has nothing to do with loading data etc into the grid, just openening and closing the window is already enough to get an issue with the memory

thanks in advance to reply

Dirk

January 27, 2010 at 11:03 am #92378

dirk
Participant

hello,

I have been investigating further, but the same issue arise with firefox (3.5) as well, only in a smaller way.

Do you have any idea on how to solve this. I did a ‘refresh’ of the same page, lest say 50 times, and the memory did not go up. only when you close and open the window via window.open() it goes up very very quick. Is there a way to get official support for this? I’m evaluating your product for purchasing, after a series of test the memory is the only one left open.

do you have some pointers or areas to look into to see what is causing this? (i have already tried the new jquery 1.4, but the issue is still the same). so in this case it has nothing to do with loading data etc into the grid, just openening and closing the window is already enough to get an issue with the memory

thanks in advance to reply

Dirk

January 27, 2010 at 4:56 pm #92383

dirk
Participant

hello,

do you mean the gridunload() function?

January 28, 2010 at 5:54 pm #92423

tony
Keymaster

Hello,

Could you please make the following test.

In the window.open do not use jqGrid, but let say a lot of things like tabs or accordeon or so on. Is the memory released after you close the window the same way as you do it with jqGrid?

Best Regsrds

Tony

February 8, 2010 at 5:15 pm #92600

dirk
Participant

I beleive I found the issue. It was related to a bunch of addons that where causing the momory not to be released. After I throw themaway it was ok

thanks

dirk
Author

Replies