search

bufanliu / flexlib

Automatically exported from code.google.com/p/flexlib
0 stars 0 forks source link

Closing a mdiWindow raises memory usage instead of lowering it #300

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. do some kind of memory monitoring (via as or profiling)
2. keep an eye on the memory chart while closing a window

What is the expected output? What do you see instead?
Every instance/listener should be released, while instances of mdiWindows
remain and if you open->close->open->close the same window more than once
you can clearly see in the profiler all the old instances, that won't be
garbage collected

What version of the product are you using? On what operating system?
latest, winXP, jbossEAP seam, flamingo 1.8

Please provide any additional information below.

I did a couple of "module" flex application, and a simple menu to let the
user open these modules dynamically (a customModuleLoader) into a
mdiWindow. Nothing gets disposed. No matter if I remove the module-loading
related stuff, mdiWindow instances never gets collected or really disposed.
The strange thing is the memory consumption raising high when you close a win.

Original issue reported on code.google.com by paolo.ru...@gmail.com on 29 Apr 2010 at 3:11

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I also experience this same exact issue. There are some memory issues with MDI 
for certain

Original comment by KoldFu...@gmail.com on 29 Sep 2010 at 4:10

GoogleCodeExporter commented 8 years ago 
I have the same problem.

Original comment by IvanHa...@gmail.com on 25 Nov 2010 at 6:54

GoogleCodeExporter commented 8 years ago 
Same here.. any feedback on this?

Original comment by ric.rodr...@gmail.com on 26 Nov 2010 at 8:54