[Qt-interest] 6 second delay after destruction of QMainWindowsubclass

[Scott Aron Bloom]

Step through the destructor to see where the breakdown is…

 

I once had this problem, because I had way way too many connections on the main window

 

Scott

 

From: qt-interest-bounces at trolltech.com [mailto:qt-interest-bounces at trolltech.com] On Behalf Of Stephen Collyer
Sent: Wednesday, May 13, 2009 3:23 AM
To: qtInterest
Subject: [Qt-interest] 6 second delay after destruction of QMainWindowsubclass

 

I have code which constructs an auto object which is subclassed from QMainWindow. Logging shows me that there is a 6 second delay after the object's destructor runs, when the program terminates.

The code in skeleton looks like:

try
{
    QApplication app(argc, argv);

    MainWindowClass m;

    <construct other objects>
    ...
}
catch(..)
{
  ..
}

<some logging>
exit(0);

The MainWindowClass object is the last object destroyed when control leaves the try block.
Can anyone suggest what's going on here ?

-- 
Stephen Collyer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090513/88f5f69d/attachment.html