Hi,
I'm having some trouble identifying the potential cause for this crash:
Tarsnap(7631,0x7fff734b5000) malloc: *** error for object 0x7fff5fbfb4a8:
pointer being freed was not allocated
--
frame #2: 0x00007fff84e316e7 libsystem_c.dylib`abort + 129
frame #3: 0x00007fff877d9070 libsystem_malloc.dylib`free + 425
frame #4: 0x00000001004eb5f2 QtWidgets_debug`QMenu::~QMenu() + 34
frame #5: 0x000000010208079b QtCore_debug`QObjectPrivate::deleteChildren()
+ 235
frame #6: 0x0000000100323d7e QtWidgets_debug`QWidget::~QWidget() + 1934
frame #7: 0x0000000100324775 QtWidgets_debug`QWidget::~QWidget() + 21
frame #8: 0x00000001000c22c5
Tarsnap`JobListItem::~JobListItem(this=0x0000000111d0d550) + 85 at
joblistitem.h:14
frame #9: 0x00000001000c21d5
Tarsnap`JobListItem::~JobListItem(this=0x0000000111d0d550) + 21 at
joblistitem.h:14
frame #10: 0x00000001000c21f9
Tarsnap`JobListItem::~JobListItem(this=0x0000000111d0d550) + 25 at
joblistitem.h:14
frame #11: 0x000000010003a5a4
Tarsnap`JobListWidget::deleteItem(this=0x000000010db698f0) + 1204 at
joblistwidget.cpp:137
...
----
http://paste.debian.net/342911/
https://github.com/Tarsnap/tarsnap-gui/blob/new-signal-slot-syntax/src/widgets/joblistwidget.cpp#L138
The QMenu in question must be the one from which I initiate the delete action
for the item. To me it looks like a race condition trigger since I upgraded my
CONNECT syntax to the new one which I think fails faster in this case. Using
the old connect syntax doesn't yield this crash.
Attempts deleteLater, removeItemWidget, shit affected code around didn't change
a thing. Any ideas what should I turn to next for resolving this? Does this
look like a Qt issue or logic on my side?
Cheers,
Shinnok
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
