Bug 409747 - Crash + data loss
Summary: Crash + data loss
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Code completion (other bugs)
Version First Reported In: 5.3.1
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-12 16:30 UTC by Wood
Modified: 2022-10-23 05:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wood 2019-07-12 16:30:41 UTC
Kdevelop crashed in libclang while auto-completing. The biggest issue is that after crashing, the entire file I was working on was deleted (the file has a size 0 on disk). Unfortunately those crashes seem kind of random and very hard to reproduce.

Callstack:

#0  0x00007f829c15db14 in clang::Lexer::LexTokenInternal(clang::Token&, bool) () from    libclang.so.6
#1  0x00007f829be6e9a7 in clang_tokenize () from    libclang.so.6
#2  0x00007f829e0b57ba in ClangCodeCompletionContext::isValidPosition(CXTranslationUnitImpl*, void*) const () from    libKDevClangPrivate.so.31
#3  0x00007f829e0b6a63 in ClangCodeCompletionContext::ClangCodeCompletionContext(KDevelop::DUChainPointer<KDevelop::DUContext> const&, QExplicitlySharedDataPointer<ParseSessionData> const&, QUrl const&, KTextEditor::Cursor const&, QString const&, QString const&) () from    libKDevClangPrivate.so.31
#4  0x00007f829e0c19f9 in (anonymous namespace)::ClangCodeCompletionWorker::run() () from    libKDevClangPrivate.so.31
#5  0x00007f82c5c710eb in QMetaObject::activate(QObject*, int, int, void**) () from    libQt5Core.so.5
#6  0x00007f82c5c7d677 in QTimer::timeout(QTimer::QPrivateSignal) () from    libQt5Core.so.5
#7  0x00007f82c5c7d958 in QTimer::timerEvent(QTimerEvent*) () from    libQt5Core.so.5
#8  0x00007f82c5c71cbb in QObject::event(QEvent*) () from    libQt5Core.so.5
#9  0x00007f82c6f0fd1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from    libQt5Widgets.so.5
#10 0x00007f82c6f17021 in QApplication::notify(QObject*, QEvent*) () from    libQt5Widgets.so.5
#11 0x00007f82c5c45988 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from    libQt5Core.so.5
#12 0x00007f82c5c987de in QTimerInfoList::activateTimers() () from    libQt5Core.so.5
#13 0x00007f82c5c9674a in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from    libQt5Core.so.5
#14 0x00007f82c5c43fda in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from    libQt5Core.so.5
#15 0x00007f82c5a6e74b in QThread::exec() () from    libQt5Core.so.5
#16 0x00007f82cbda8dec in KDevelop::CompletionWorkerThread::run() () from    libKDevPlatformLanguage.so.53
#17 0x00007f82c5a733aa in ?? () from    libQt5Core.so.5
#18 0x0000003979407aa1 in start_thread () from /lib64/libpthread.so.0
#19 0x0000003978ce8aad in clone () from /lib64/libc.so.6
Comment 1 Marco polo 2019-08-02 15:18:46 UTC
Just encountered this bug.

kdevelop crashed with

'/tmp/.mount_KDevelL7pxbl/AppRun: line 36: 12625 Bus error(core dumped) kdevelop $@'

the file that was been edited was zeroed out.

there was no call stack output.
Comment 2 Justin Zobel 2022-09-23 02:22:55 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-08 04:53:23 UTC
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
mark the bug 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!
Comment 4 Bug Janitor Service 2022-10-23 05:01:14 UTC
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!