I should explain more specifically:
I am placing a new Widget pointer (call it widgetA) in a struct-like QObject class. (all data members public)
That widgetA performs a function, sends a signal to the struct-like Qobject's creator, who then deletes the widgetA and the struct-like widget.
The signal being received is a unique variable to that object that allows me to search a list for the object while under the protection of a mutex locker.
In this case the VS .NET would complain on the very next new memory allocation about a heap corruption.
If I use deleteLater on the widgetA and then also on the struct-like Qobject, it no longer has this issue.
Bookmarks