| Summary: | Crash after opening another file | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Martin Flöser <mgraesslin> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | alex.danila.web, bclawilkinson+kdebugs, exabyte, pfuetz, yaxattax |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Martin Flöser
2011-12-09 18:05:11 UTC
Created attachment 67966 [details]
New crash information added by DrKonqi
kate (3.7.4) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.0
- What I was doing when the application crashed:
The crash happens every time I start Kate loading a specific Kate session. The only difference between the session that causes the crash and the other Kate sessions that work fine is that this specific one contains many source files (44) from many different locations, including two source trees and ~/.config
-- Backtrace (Reduced):
#6 0x00007f4a571f5118 in effectiveAdvance (item=<optimized out>, this=<synthetic pointer>) at text/qtextengine_p.h:220
#7 QTextLine::cursorToX (this=0x7fff4a4a0f30, cursorPos=0x7fff4a4a0f6c, edge=<optimized out>) at text/qtextlayout.cpp:2582
#8 0x00007f4a3d32a919 in cursorToX (edge=QTextLine::Leading, cursorPos=8, this=0x7fff4a4a0f30) at /usr/include/qt4/QtGui/qtextlayout.h:219
#9 KateRenderer::layoutLine (this=0x2f4f280, lineLayout=..., maxwidth=0, cacheLayout=<optimized out>) at ../../part/render/katerenderer.cpp:961
#10 0x00007f4a3d32f1ad in KateLayoutCache::line (this=0x2f504a0, realLine=279, virtualLine=279) at ../../part/render/katelayoutcache.cpp:314
*** Bug 291949 has been marked as a duplicate of this bug. *** Martin, is this still an issue??? Given the other duplicate reports, the reason seems to be Qt 4.8... (In reply to comment #3) > Martin, is this still an issue??? I did not hit the crash anymore since the report. So I cannot say whether it is still an issue or not. Sorry. *** Bug 292122 has been marked as a duplicate of this bug. *** Here's a diff between a crashing session and a non-crashing session. The content of the TODO file doesn't matter. --- /home/milko/.kde/share/apps/kate/sessions/OntMerge2.katesession.working 2012-01-23 22:11:06.759744982 +0200 +++ /home/milko/.kde/share/apps/kate/sessions/OntMerge2.katesession 2012-01-23 22:11:24.355848423 +0200 @@ -322,6 +322,15 @@ ReadWrite=true URL=file:///home/milko/Документи/Програмиране/Биоинформатика/pawnets/setup.py +[Document 41] +Bookmarks= +Encoding=UTF-8 +Highlighting=None +Indentation Mode=0 +Mode= +ReadWrite=true +URL=file:///home/milko/Документи/Програмиране/Биоинформатика/ontmerge2/TODO + [Document 5] Bookmarks= Encoding=UTF-8 @@ -434,10 +443,10 @@ Sizes=574,590 [MainWindow0-ViewSpace 0] -Active View=file:///home/milko/Документи/Програмиране/Биоинформатика/pawnets/setup.py -Count=1 +Active View=file:///home/milko/Документи/Програмиране/Биоинформатика/ontmerge2/TODO +Count=2 View 0=file:///home/milko/Документи/Програмиране/Биоинформатика/pawnets/setup.py -View 1=file:///home/milko/Документи/Програмиране/Биоинформатика/pawnets/setup.py +View 1=file:///home/milko/Документи/Програмиране/Биоинформатика/ontmerge2/TODO View 10=file:///home/milko/Документи/Програмиране/Биоинформатика/ontmerge2/TODO View 11=file:///home/milko/Документи/Програмиране/Биоинформатика/ontmerge2/ontmerge2/references/fma.py View 12=file:///home/milko/Документи/Програмиране/Биоинформатика/ontmerge2/ontmerge2/ui/predictions.py @@ -691,7 +700,7 @@ CursorLine=45 [Open Documents] -Count=41 +Count=42 [Open MainWindows] Count=1 OK, it has nothing to do with which file is in the session, it has to do with which file is active. If I open the TODO file (leaving it active) and reload, there's a crash. If I switch to another file before I reload, there's no crash. In that case, can you attach the TODO file? *** Bug 294477 has been marked as a duplicate of this bug. *** *** Bug 294992 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 292947 *** |