Summary: | kate crashes when doing regexp search & replace (Replace All) on large file (KateLineLayout::viewLineCount (this=0x0)) | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Peter Schübel <peter.schuebel> |
Component: | part | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | christoph, pierigno |
Priority: | VHI | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Peter Schübel
2011-02-10 15:21:44 UTC
Peter: Can you please attach the file, so that we can reproduce as well? This is really important. There are several other bug reports with a similar crash, but it always happens randomly. So having a way to reproduce would help immensely to solve this issue! Although some of the bugs were due to folding, this looks like another issue: In KateLineLayout, m_layout pointer is 0x0. With setLayout() and invalidateLayout() m_layout is set to 0x0. So maybe this is called somehow, and then KateLineLayout::viewLineCount( ) is called that accesses the m_layout without check. In KateLineLayout::viewLine( int viewLine ), there is even a call Q_ASSERT(isValid()); and isValid() checks m_layout(). So question is why the layout is 0, this seems to be wrong... I think the problem is due to a wrong management of large sequence of non-blank character. Try for example to select all the text of this non-formatted rss file: http://pkg.sabayon.org/standard/sabayon-limbo/database/x86/5/updates.rss Here, on a core i7 with 6Gb of ram, kate makes the whole system slugghish and unresponsive, until you tell kate to indent it. If it is the "large line" problem, we can't fix that, this is an qt issue. We need to layout the whole line. Therefore closing, if somebody provides way to reproduce, we can look again at this. 100KB files or co seem no problem for me, but slow. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |