Summary: | Crash in marker cleanup code [QList::*, IRCView::cullMarkedLine] | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Modestas Vainius <modax> |
Component: | ircview | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | antoine.mechelynck, b.buschinski, bruno, bugs.kde.org3, code.jtr, cody, demopley, dvratil, hein, hsr.desktop, keever, konversation-devel, kristjan.ugrin, luke-jr+kdebugs, rc.dunphy, rdieter, scott, sean.s.85, spindlerline, valir, wk, wstephenson, xejakig884 |
Priority: | NOR | ||
Version: | 1.2 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Modestas Vainius
2009-10-10 19:53:46 UTC
*** Bug 214514 has been marked as a duplicate of this bug. *** *** Bug 281663 has been marked as a duplicate of this bug. *** *** Bug 281874 has been marked as a duplicate of this bug. *** Created attachment 63629 [details]
New crash information added by DrKonqi
konversation (1.3.1) on KDE Platform 4.7.41 (4.7.41 (KDE 4.8 >= 20110807) using Qt 4.7.4
I can confirm this crash, happend to me a few times already, always when Konversation was minimized in tray. My backtrace is slightly different, maybe it will make it easier to track down the cause of the crash.
-- Backtrace (Reduced):
#11 0x00000000005044c5 in QList<QTextBlock>::first (this=0x19685b8) at /usr/include/QtCore/qlist.h:269
#12 0x00000000005045ac in QList<QTextBlock>::takeFirst (this=0x19685b8) at /usr/include/QtCore/qlist.h:477
#13 0x0000000000503579 in IRCView::cullMarkedLine (this=0x1968580, where=<optimized out>, rem=<optimized out>, add=<optimized out>) at /tmp/yaourt-tmp-progdan/abs-konversation/src/konversation-1.3.1/src/viewer/ircview.cpp:474
#14 0x0000000000446feb in IRCView::qt_metacall (this=0x1968580, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffc4bb5640) at /tmp/yaourt-tmp-progdan/abs-konversation/src/build/src/moc_ircview.cpp:224
[...]
#16 0x00007f96d7d77b6a in QTextDocument::contentsChange(int, int, int) () from /usr/lib/libQtGui.so.4
*** Bug 282576 has been marked as a duplicate of this bug. *** *** Bug 282971 has been marked as a duplicate of this bug. *** Git commit cbe876c954b5deaf1a6729b7123d6880df4513ee by eli mackenzie. Committed on 30/09/2011 at 12:41. Pushed by argonel into branch 'master'. Changed method of remember/marker line tracking. Qt 4.7.4 introduces a change to the handling of QTextBlock::userState that makes it unusable for the purposes of tracking which block represents a marker or remember line. Previous versions of Qt also changed or otherwise corrupted the userState value causing the loss of synchronization with the data held in the IRCView itself. Blocks are now tracked via the userData field, which was unmolested in the change made to QTextDocument. Warning: this commit introduces a large volume of debugging output. For more information about the Qt change, see QTBUG-20916. BUG: 210106 CCBUG: 260598 M +1 -1 src/commit.h M +17 -0 src/irc/outputfilter.cpp M +1 -0 src/irc/outputfilter.h M +278 -95 src/viewer/ircview.cpp M +16 -9 src/viewer/ircview.h http://commits.kde.org/konversation/cbe876c954b5deaf1a6729b7123d6880df4513ee *** Bug 283231 has been marked as a duplicate of this bug. *** *** Bug 283717 has been marked as a duplicate of this bug. *** Can you backport this fix to 1.3.1? Although the patch applies with a bit of tickling, build fails because OutputFilterInput::context is not present in the 1.3.1 codebase. *** Bug 283890 has been marked as a duplicate of this bug. *** *** Bug 283891 has been marked as a duplicate of this bug. *** Will: We'll be making the fix available for 1.3.1 on a branch in konversation.git soon. Eli will post the details when it's done. We won't be able to officially support Konversation builds using it, however. Hopefully the 1.4 release won't be that long now, either. Git commit 4a9627ef625342b450b1101ac1575bab44b5641a by eli mackenzie. Committed on 30/09/2011 at 12:41. Pushed by argonel into branch '1.3.1'. reformulation of cbe876c for v1.3.1 CCBUG:210106 M +12 -0 ChangeLog M +1 -1 src/commit.h M +1 -1 src/version.h M +103 -103 src/viewer/ircview.cpp M +16 -9 src/viewer/ircview.h http://commits.kde.org/konversation/4a9627ef625342b450b1101ac1575bab44b5641a *** Bug 284077 has been marked as a duplicate of this bug. *** *** Bug 284614 has been marked as a duplicate of this bug. *** *** Bug 284665 has been marked as a duplicate of this bug. *** [ 4 emails per report is too many ] *** Bug 285578 has been marked as a duplicate of this bug. *** Created attachment 65215 [details]
New crash information added by DrKonqi
konversation (1.3.1) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
My KDE come from KDF repository, up to date.
Don't know if the patch has already been applied ?
Normally yes, during one week no crash appear, now it always crash during the night.
Will, did we get a regression somewhere on obs ?
-- Backtrace (Reduced):
#6 0x00007ffc08cb6d95 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007ffc08cb82ab in __GI_abort () at abort.c:93
[...]
#9 0x00007ffc08cf6c06 in malloc_printerr (action=3, str=0x7ffc08dcd77b "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
#10 0x0000000000524171 in node_destruct (n=0x105ee48, this=<optimized out>) at /usr/include/QtCore/qlist.h:375
#11 erase (it=<optimized out>, this=<optimized out>) at /usr/include/QtCore/qlist.h:452
Created attachment 65329 [details]
New crash information added by DrKonqi
konversation (1.3.1) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed: Seems that on openSUSE KDF 4.7.3 the patch is not included, or has a problem somewhere.
I get that each morning, after letting konversation alone open during the night
-- Backtrace (Reduced):
#6 0x00007f72bab86d95 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f72bab882ab in __GI_abort () at abort.c:93
[...]
#9 0x00007f72babc6c06 in malloc_printerr (action=3, str=0x7f72bac9d77b "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
#10 0x0000000000524171 in node_destruct (n=0x120f8b8, this=<optimized out>) at /usr/include/QtCore/qlist.h:375
#11 erase (it=<optimized out>, this=<optimized out>) at /usr/include/QtCore/qlist.h:452
*** Bug 286092 has been marked as a duplicate of this bug. *** *** Bug 286805 has been marked as a duplicate of this bug. *** *** Bug 286951 has been marked as a duplicate of this bug. *** Created attachment 65850 [details]
New crash information added by DrKonqi
konversation (1.3.1) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed: Sorry I'm now on 12.2 (factory) with KDF during one week I didn't get crash now with new build this one start to reappear.
We have a regression! or a patch is forget during the obs build.
Will can have you a look at it ? Thanks.
-- Backtrace (Reduced):
#6 0x00007f8b6ebdfd15 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f8b6ebe122b in __GI_abort () at abort.c:93
[...]
#9 0x00007f8b6ec1fb86 in malloc_printerr (action=3, str=0x7f8b6ecf66fb "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
#10 0x0000000000524171 in node_destruct (n=0x2ce7608, this=<optimized out>) at /usr/include/QtCore/qlist.h:375
#11 erase (it=<optimized out>, this=<optimized out>) at /usr/include/QtCore/qlist.h:452
*** Bug 287269 has been marked as a duplicate of this bug. *** Git commit 72111c725e35ce8c98933f768f9c826a5ad7a55d by Eike Hein. Committed on 28/11/2011 at 20:46. Pushed by hein into branch 'master'. Clean up line breaks in app description. BUG:210106 M +2 -3 src/main.cpp http://commits.kde.org/konversation/72111c725e35ce8c98933f768f9c826a5ad7a55d Sorry about that, wrong bug number due to a clipboard problem with NX. *** Bug 291478 has been marked as a duplicate of this bug. *** |