search

pkt1583 / gwt-ext

Automatically exported from code.google.com/p/gwt-ext
0 stars 0 forks source link

Memory leak creating and closing Windows #360

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a button that opens a Modal Window
2. Close the window
3. Repeat the process

What is the expected output? What do you see instead?
The problem is that aparently memory allocated in each iteration is never 
garbage collected

What version of the product are you using? On what operating system?
ext-2.0.2
gwtext-2.0.4
gwt-windows-1.5.0 (rc1)
Internet Explorer, 6.0.2900.2180.xpsp_sp2
Mozilla Firefox, Mozilla/5.0 Gecko/20080404 Firefox/2.0.0.14

Please provide any additional information below.

Thread:
http://groups.google.com/group/gwt-
ext/browse_thread/thread/4c771c4b7f0d4244

Original issue reported on code.google.com by matias.g...@gmail.com on 26 Jun 2008 at 10:42

GoogleCodeExporter commented 8 years ago 
Please, this issue has been confirmed as bug? Or is it a miss use of the 
library? 
Our whole appication depends on this. 

Regards,
Matias G. Rodriguez

Original comment by matias.g...@gmail.com on 14 Oct 2008 at 4:01

GoogleCodeExporter commented 8 years ago 
I've replicated this just using extjs.  I'm trying to find out what objects are 
not 
claimed by the GC but at first look it seems that there are quite a few of them.

Original comment by mlim1...@gmail.com on 20 Oct 2008 at 10:43

GoogleCodeExporter commented 8 years ago 

Is there anything else we can do to help?

Regards
Matias G. Rodriguez

Original comment by matias.g...@gmail.com on 3 Nov 2008 at 8:04

GoogleCodeExporter commented 8 years ago 
A few pointers here:
- Doug is using a different paradigm to workaround this issue.
http://gwt-ext.com/forum/viewtopic.php?f=5&t=3206&p=10478
- A patch was issued here to address some memory issues by a extjs user:
http://extjs.com/forum/showthread.php?t=45782
  I tried the patch and it does reduce the memory footprint on creating 
windows/panels.  However it still have some more left.

Original comment by mlim1...@gmail.com on 9 Nov 2008 at 9:06

GoogleCodeExporter commented 8 years ago 
I got (also) a big memory leak problem in our app... with GWT 1.5.3 + GWT-EXT 
lastest
(+extjs 2.0.2)

As the guig's patch is based on extjs 2.2, I think we can't use it with gwt-ext
because of the f***ing famous licence change...

don't you think the same ?

And the Doug way of coding GWT app seems to be a good way to solve the problem 
but i
can't apply this to my app ! It is a good tips but not an acceptable solution
(nagivation dispatching with the entrypoint...).

What is the solution to get the memory back when opening and closing tabs ????

My boss is going to ask us to remove all the tabs from the application if we 
can't
find any valid solution.... please help !

Original comment by cyril.la...@gmail.com on 5 Jan 2009 at 4:03

GoogleCodeExporter commented 8 years ago 
Is there any updates for this issues.
We are waiting for the patch

Original comment by karthike...@googlemail.com on 20 Apr 2009 at 5:42