From kde-core-devel Wed Mar 01 00:09:49 2000 From: David Faure Date: Wed, 01 Mar 2000 00:09:49 +0000 To: kde-core-devel Subject: More hints on that long-lasting QIconView crash X-MARC-Message: https://marc.info/?l=kde-core-devel&m=95186949818375 As most of you know, alas, konqueror has a very nasty bug, making it crash sometimes when clicking on a file (like a text file) that opens a new view, because somehow something happens in the already-deleted icon view. I tracked it down, finally ! On a mouseReleaseEvent, QIconView does: emit mouseButtonClicked( e->button(), item, e->globalPos() ); emit clicked( item ); emit clicked( item, e->globalPos() ); Since the first one (or the second, didn't check) deletes the iconview (in konqueror, which switches to another view), when it comes back here, the third emit looks into a deleted list of receivers, hence the crash... No idea what a possible fix could be, though... (or it would be hacky, like relying on the order those emits are done). Reggie ? Is it wrong for konqueror to connect to more than one of those signals ? -- David FAURE david@mandrakesoft.com, faure@kde.org http://home.clara.net/faure/ KDE, Making The Future of Computing Available Today