Qt Application Slowing Down

mrjj

@swansorter
Ok. That's pretty fast.
Does seems related to navigating the app.
I would set breakpoints in all dialogs destructors to make sure they are deleted.
and generally, look over the code verify that you free stuff.

SGaist

Hi,

From the look of the code you posted, you are re-creating at least your main window each time you call your settings dialog. If you do that with all your dialogs and maybe other widgets, it's not really surprising that the memory gets eaten up.

You should take a look at the more complex Qt example on how to handle a QMainWindow with one or more dialogs.

Still based on your code and ve fact that you are using images, how are you handling them ?

swansorter

@SGaist i searched but found nothing ...
please share the link of any Qt example program

Christian Ehrlicher

@swansorter said in Qt Application Slowing Down:

please share the link of any Qt example program

https://doc.qt.io/qt-5/examples-widgets.html

swansorter

@Christian-Ehrlicher i need example like QMainWindow with two or more dialogs.

SGaist

Having two dialogs or one doesn't change things much.

What do you search exactly with an example with two dialogs ?

swansorter

@SGaist yea...qt dialog with more than two dialog

jsulm

@swansorter If you can create one dialog you can create 2 or 3 or 4 or ...
So, what exactly is the problem?

swansorter

@jsulm 1. we have different screens like home screen ,setting screen ,main sort screen , resort1 ,resort2 and resort 3 screens
2.On "home screen" we have setting button.
3.we move to the "setting screen" with code like the following:-

settingDialog *sd=new settingDialog(this);
sd->setModal(true);
close(); //closes the home window
sd->setAttribute( Qt::WA_DeleteOnClose);
sd->exec();//shows the setting screen

4.On "Setting screen" we have main sort screen Button ,resort1 ,2 ,3 screen buttons to move respective screens.

5.we move to the "main sort screen" with code like the following:-

mainSortDialog *ms=new mainSortDialog();
ms->setModal(true);
ms->setAttribute ( Qt::WA_DeleteOnClose, true );
this->close();//closes the setting screen
ms->exec();//shows the main sort window

6.on "main sort screen" we have Back button to go back to "setting screen".

we move to the "main sort screen" with code like the following:-

sd=new settingDialog();
sd->setAttribute ( Qt::WA_DeleteOnClose, true );
sd->setModal(true);
this->close();//closes the main sort screen
sd->exec();//shows the setting screen

8.if i do the step 5 and 7 continuously the application gets slower .

jsulm

@swansorter said in Qt Application Slowing Down:

if i do the step 5 and 7 continuously the application gets slower

Then you have to investigate.
Did you check CPU usage of your app?
Did you check RAM usage of your app?

mrjj

Hi
Also did you CHECK that your dialogs are in fact - deleted?
By breakpoints in their destructors.
WA_DeleteOnClose should take care of that but its good to check.

swansorter

@mrjj yea checked.....execution of destructors are happening only when i moved to main window

mrjj

@swansorter

Well is that the issue then?
If you dont move to mainwin, they are not freed,
so if u never do that then it grows.
or ?

swansorter

@mrjj yes that is the issu..
how to free the object when the perticular screen "dialog" close?

mrjj

@swansorter
well first of all you can clean up the places where newing is not needed.
All places where you use exec() for dialogs could just be

void class::insomefunc() {
mainSortDialog ms;
this->close();//closes the setting screen
ms->exec();
}

and it would be cleaned up as soon as dialog is closed.
So unless you are not using exec() there should be no reason to new it.
and hence that could auto clean lots for you.

swansorter

@mrjj i tried this one ... working for me
thank you

mrjj

@swansorter
Good. hopefully it can also cure the leaking.

swansorter

@mrjj i used breakpoints on distructor
if i use close()...they are not freed
only if remove close()....they get cleared

mrjj

@swansorter

Im not sure in what context.

if using something like

void class::insomefunc() {
mainSortDialog ms;
this->close();//closes the setting screen
ms->exec();
}

MS should always be deleted. the this->close() should have no effect.

If you use new for other classes make sure it still has WA_DeleteOnClose.

swansorter

@mrjj
am using this one move to main sort
void class::insomefunc() {
mainSortDialog ms;
ms->exec();
}
and back to main screen by using just "hide();" in back button
this is work for me even the memory leakage.
but if use close(); its not working
void class::insomefunc() {
mainSortDialog ms;
this->close();//closes the setting screen
ms->exec();
}