QTableWidget Crash in Destructor

[mclark]

This one appears unsolvable so I'll just have to change my design. I'll collect all notifications in the main app. When the dialog is constructed, the table will only contain a snapshot of devices known at the time of dialog instantiation.

The table in the dialog will not be updated dynamically. Not a big deal but the original problem still irritates...

Thanks to all who tried to help!

[wysota]

But do you use more than one thread in your application?

[mclark]

But do you use more than one thread in your application?

Yes, multiple threads are running in the app. In the offending dialog, a notification thread was running. The notification handler was locked using a QMutexLocker, where the mutex was declared as a class member. This should protect the table insertion code, no?

QMutexLocker locker( &m_NotifyMutex );

QMutexLocker locker( &m_NotifyMutex );

To copy to clipboard, switch view to plain text mode 

[wysota]

You can't access QObjects from more than one thread and no mutex will help here. You have to make sure that you follow that rule.