Bug 431796

Summary:	kdevelop segmentation fault loading a project
Product:	[Applications] kdevelop	Reporter:	gjditchfield
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	igorkuo, mail, sknauss
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description gjditchfield 2021-01-18 20:43:54 UTC

SUMMARY
I'm using the KDE PIM docker image, with the packaged kdevelop (not compiled locally). KDevelop 5.6.40.

KDevelop had been stable until I ran `apt update; apt full-upgrade` two days ago. Now it frequently crashes when loading projects. This is repeatable today:

STEPS TO REPRODUCE
1. apt update and full-upgrade. kdesrc-build.
2. apt purge kdevelop and apt install kdevelop.
3. remove all *.kdev4 files and home/neon/kdepim/home/local/kdevelop/sessions/*
4. launch kdevelop.
5. Click "open/import project...".
6. Open /home/neon/kdepim/src/kde/pim/eventviews with the CMake project manager.

OBSERVED RESULT
The build window says that generation is done and the progress bar starts counting up from 0%, then kdevelop crashes. The crash handler does not appear. The output to stderr that appears after I start the import is
-------
kdevplatform.shell: Could not load plugin "kdevbazaar" , it reported the error: "Unable to find Bazaar (bzr) executable. Is it installed on the system?" Disabling the plugin now.
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 60 and type 'Read', disabling...
QSocketNotifier: Invalid socket 73 and type 'Read', disabling...
QSocketNotifier: Invalid socket 64 and type 'Read', disabling...
QSocketNotifier: Invalid socket 68 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 70 and type 'Read', disabling...
QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
QSocketNotifier: Invalid socket 28 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
The X11 connection broke (error 1). Did the X11 server die?
FunctionDeclarationData::m_defaultParameters There were items left on destruction: 180
ClassFunctionDeclarationData::m_defaultParameters There were items left on destruction: 1898
ClassDeclarationData::baseClasses There were items left on destruction: 954
DUContextData::m_uses There were items left on destruction: 32387
TopDUContextData::m_usedDeclarationIds There were items left on destruction: 512
MacroDefinitionData::parameters There were items left on destruction: 658
DUContextData::m_importers There were items left on destruction: 982
DUContextData::m_importedContexts There were items left on destruction: 4126
DUContextData::m_childContexts There were items left on destruction: 15661
corrupted double-linked list
Re-raising signal for core dump handling.
Segmentation fault
-----------

SOFTWARE/OS VERSIONS

KDE Frameworks Version: 5.79
Qt Version: 5.15.2

Comment 1 Igor Kushnir 2021-01-19 14:48:17 UTC

This is probably one of the two recent KDevelop regressions: Bug 431391 (possibly worked around by today's commit https://commits.kde.org/kdevelop/642fc99e0de8a3aba3a20762fb34eb9e3281c74e) or Bug 431811 (the bug report contains a workaround).

Comment 2 gjditchfield 2021-01-19 21:11:34 UTC

The work-around mentioned in bug 431391 (disabling Background Parser in Settings->Configure KDevelop) stops most crashes.

Comment 3 gjditchfield 2021-01-21 21:50:45 UTC

Still crashing in kdevelop 4:5.6.1+p20.04+git20210121.0643-0

Comment 4 Sandro Knauß 2021-01-21 22:00:35 UTC

Possible merge candidate: https://bugs.kde.org/show_bug.cgi?id=431887

I also use the KDE PIM docker image.

Comment 5 gjditchfield 2021-01-21 23:02:05 UTC

That commit is on master.  If the devs merge it to the 5.6 branch, will it show up in the KDE PIM docker image?

Comment 6 Francis Herne 2021-01-21 23:12:03 UTC

The version numbering is perhaps misleading. The version number of `master` is 5.6.40, and that's the version you're using.

(this numbering is common to most KDE applications -- betas will be 5.6.80+, RCs 5.6.90+).

Today's Neon package already includes Milian's attempted fix, which unfortunately doesn't seem to work for another reporter.

The new feature triggering this bug is not in the 5.6 branch so there's no reason to backport any fixes to it.

*** This bug has been marked as a duplicate of bug 431391 ***