https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #14 from RJVB <rjvber...@gmail.com> --- Now this is extra interesting: after sending off my previous comment and quitting DrKonqi, the crashed KDevelop made a more or less clean exit, judging from terminal output. It might even have able to continue to work if the X11 connection hadn't been interrupted for too long by DrKonqi: The X11 connection broke (error 1). Did the X11 server die? MacroDefinitionData::parameters There were items left on destruction: 1 ClassDeclarationData::baseClasses There were items left on destruction: 1 FunctionDeclarationData::m_defaultParameters There were items left on destruction: 9 TopDUContextData::m_usedDeclarationIds There were items left on destruction: 11 DUContextData::m_uses There were items left on destruction: 64 DUContextData::m_importers There were items left on destruction: 18 TopDUContextData::m_problems There were items left on destruction: 9 DUContextData::m_localDeclarations There were items left on destruction: 55 DUContextData::m_childContexts There were items left on destruction: 44 DUContextData::m_importedContexts There were items left on destruction: 43 ProblemData::diagnostics There were items left on destruction: 225 register count: 0, destroy count 0: average LZ4 compression ratio: 1.96008; 114 compressed of 114 [2] Exit 1 kdevelop5 --ps -- You are receiving this mail because: You are watching all bug changes.
