| Summary: | Q_ASSERT in Kate::TextBlock while editing a file in KDevelop | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Daniel Vrátil <dvratil> |
| Component: | part | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | christoph, jtamate |
| Priority: | NOR | ||
| Version First Reported In: | Git | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Daniel Vrátil
2017-02-01 20:15:54 UTC
By default, a text buffer block initially contains 64 lines. In the backtrace, we can see that line 427 finally maps to line 62 in the requested text block. Given a default size of 64 lines, this looks feasible... A wild guess: One possible explanation is that KDevelop somehow accesses the text buffer from different threads, and therefore messes up the text buffer. Then, things like this could happen. Therefore: Did you have this crash also with Kate or KWrite? => Without a way to reproduce this, we can't fix it. Sorry :( *** Bug 398573 has been marked as a duplicate of this bug. *** 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! |