1. #1
    Ext User
    Join Date
    Oct 2008
    Posts
    4
    Vote Rating
    0
    JohVle is on a distinguished road

      0  

    Default Memory leak in Dialog

    Memory leak in Dialog


    Hi all,

    I think there is a memory leak in the com.extjs.gxt.ui.client.widget.Dialog.

    Here is a little test with a button to open a number of dialogs and a button to close them afterwards. Part of the memory is not released when closing the dialogs.

    Do I have to call other cleanup methods or should dialog.close() do the job ?

    Tested on IE6, FF2 and Chrome with GWT 1.5.2 and Gxt 1.1.2.

    Code:
    public class DialogExampleEntryPoint implements EntryPoint {
    
    	private Dialog[] dialogs;
    	private int NUMBER_OF_DIALOGS = 25;
    
    	public void onModuleLoad() {
    		LayoutContainer buttonPanel = new LayoutContainer();
    		ButtonBar buttons = new ButtonBar();
    		buttons.add(new Button("Open Multiple Dialogs",
    				new SelectionListener<ComponentEvent>() {
    					public void componentSelected(ComponentEvent ce) {
    						dialogs = new Dialog[NUMBER_OF_DIALOGS];
    						for (int i = 0; i < NUMBER_OF_DIALOGS; i++) {
    							dialogs[i] = new Dialog();
    							dialogs[i].show();
    						}
    					}
    				}));
    
    		buttons.add(new Button("Close Multiple Dialogs",
    				new SelectionListener<ComponentEvent>() {
    					public void componentSelected(ComponentEvent ce) {
    						for (int i = 0; i < NUMBER_OF_DIALOGS; i++) {
    							dialogs[i].close();
    							dialogs[i] = null;
    						}
    						dialogs = null;
    					}
    				}));
    
    		buttonPanel.add(buttons);
    		RootPanel.get().add(buttonPanel);
    	}
    }

  2. #2
    Ext User
    Join Date
    Sep 2008
    Posts
    4
    Vote Rating
    0
    jules is on a distinguished road

      0  

    Default any news?

    any news?


    I got the same problem with gxt dialogs and IE6.
    Memory increases about 1-4MB each time I open a dialog and close it again. I use CloseAction.CLOSE and only gxt widgets, no DOM manipulation...

    Minimizing the browser Window an maximizing again frees most of the memory so I can start again.

    Splitting my ImageBundles as suggested here http://groups.google.com/group/Googl...f75010293a16af
    helped a lot but seems not to be the only problem

Thread Participants: 1

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar