Summary: | Kompare crashed when advancing to next file. | ||
---|---|---|---|
Product: | [Applications] kompare | Reporter: | Raúl <rasasi78> |
Component: | general | Assignee: | Kompare developers <kompare-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | alberth289346, andrea, andresbajotierra, annulen, carterqw, dario, jy_ro |
Priority: | NOR | ||
Version: | 4.0.0 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
A test patch for crashing kompare
Patch to prevent crash in this case |
Description
Raúl
2010-11-25 00:58:18 UTC
[Comment from a bug triager] This may be related to crashes in bug 202457. Regards *** Bug 269177 has been marked as a duplicate of this bug. *** Created attachment 59257 [details]
A test patch for crashing kompare
just type 'kompare cr.patch', press 'next-file' (I could not get it to work with just a removed file in the test patch)
Oh great, it did not save my comments :( Qt: 4.7.2 KDE Development Platform: 4.6.2 (4.6.2) Kompare: 4.0.0 from Fedora 15 pre-alpha, x64. I can create a stack-dump if you like (although without symbols as they would not load), but my example cr.patch file that reliably crashes kompare is probably much more useful. *** Bug 273617 has been marked as a duplicate of this bug. *** *** Bug 277050 has been marked as a duplicate of this bug. *** Created attachment 61596 [details]
Patch to prevent crash in this case
*** Bug 278951 has been marked as a duplicate of this bug. *** I don't think the proposed patch is right. As I understand it, deleting tree widget items from slotSetSelection is unsafe with the new Qt 4 tree widgets, which explains why this started showing up when the KompareNavTreePart got ported to QTreeWidget. Now that I also ported the KomparePart to the Qt 4 QTreeWidget, we're seeing the same thing there, see bug #286086. Delaying the processing of slotSetSelection until the next event loop iteration should fix it, I'll have a fix shortly. Removing CC, I'm already on kompare-devel. So this one looks different from bug #286086 after all, maybe Konstantin's patch makes sense after all, I'll have to take a closer look. *** This bug has been marked as a duplicate of bug 202457 *** |