[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-08-07 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/kdev |https://invent.kde.org/kdev
   |elop/kdevelop/-/commit/af76 |elop/kdevelop/-/commit/9df7
   |2efe10fbba04fa57f7ea789e1b3 |475127bdc3b47e5b7055b567faa
   |1dbfbcb2b   |8b01ac6b4

--- Comment #29 from Igor Kushnir  ---
Git commit 9df7475127bdc3b47e5b7055b567faa8b01ac6b4 by Igor Kushnir.
Committed on 07/08/2025 at 08:24.
Pushed by igorkushnir into branch 'release/25.08'.

Never store precompiled preambles in memory to work around a crash

Precompiled preambles are stored in RAM by default given libclang
version 17 or later, where the necessary API is available since
https://github.com/llvm/llvm-project/commit/55f7e00afc56c68421220d60d29c079b58fe9c79

As discovered in a comment thread starting at
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/777#note_1224253
the linked crash that affects many KDevelop users can be worked around
by not storing precompiled preambles in memory.

So hide the precompiled preamble storage configuration UI and never
store the preambles in memory until a proper fix is found.
FIXED-IN: 6.3.250800
(cherry picked from commit af762efe10fbba04fa57f7ea789e1b31dbfbcb2b)

M  +5-0kdevplatform/shell/settings/languagepreferences.cpp
M  +5-0plugins/clang/duchain/clangindex.cpp

https://invent.kde.org/kdevelop/kdevelop/-/commit/9df7475127bdc3b47e5b7055b567faa8b01ac6b4

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-08-07 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kdev
   ||elop/kdevelop/-/commit/af76
   ||2efe10fbba04fa57f7ea789e1b3
   ||1dbfbcb2b
   Version Fixed In||6.3.250800
 Status|ASSIGNED|RESOLVED

--- Comment #28 from Igor Kushnir  ---
Git commit af762efe10fbba04fa57f7ea789e1b31dbfbcb2b by Igor Kushnir.
Committed on 07/08/2025 at 08:20.
Pushed by igorkushnir into branch 'master'.

Never store precompiled preambles in memory to work around a crash

Precompiled preambles are stored in RAM by default given libclang
version 17 or later, where the necessary API is available since
https://github.com/llvm/llvm-project/commit/55f7e00afc56c68421220d60d29c079b58fe9c79

As discovered in a comment thread starting at
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/777#note_1224253
the linked crash that affects many KDevelop users can be worked around
by not storing precompiled preambles in memory.

So hide the precompiled preamble storage configuration UI and never
store the preambles in memory until a proper fix is found.
FIXED-IN: 6.3.250800

M  +5-0kdevplatform/shell/settings/languagepreferences.cpp
M  +5-0plugins/clang/duchain/clangindex.cpp

https://invent.kde.org/kdevelop/kdevelop/-/commit/af762efe10fbba04fa57f7ea789e1b31dbfbcb2b

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-07-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #27 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/800

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-06-17 Thread Tomas Trnka
https://bugs.kde.org/show_bug.cgi?id=486932

Tomas Trnka  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #26 from Tomas Trnka  ---
(In reply to Igor Kushnir from comment #25)
> We have found a workaround for this crash in a discussion under the MR. Open
> the Configure KDevelop dialog, and at the bottom of the Language Support
> page set "Store precompiled preambles in" to "Session Temporary Directory".

Thanks, I can confirm that this workaround makes the crash go away for me (on
kdevelop-25.04.2-1.fc42.x86_64).

I was able to reproducibly crash it five times in a row (open KDevelop on a C++
project, optionally wait for background parsing to finish, select a particular
.cpp file, start typing #include <, boom!). After flipping the "Store
precompiled preambles" setting I can't reproduce the crash any more.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-05-25 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #25 from Igor Kushnir  ---
(In reply to Bug Janitor Service from comment #24)
> A possibly relevant merge request was started @
> https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/777
We have found a workaround for this crash in a discussion under the MR. Open
the Configure KDevelop dialog, and at the bottom of the Language Support page
set "Store precompiled preambles in" to "Session Temporary Directory".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-05-24 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=486932

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #24 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/777

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-05-04 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #23 from Igor Kushnir  ---
*** Bug 503743 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-04-18 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #22 from Igor Kushnir  ---
*** Bug 502955 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-04-17 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=486932

David Redondo  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #21 from David Redondo  ---
I just had the crash when adding a using namespace at the top of the file

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-04-15 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #20 from Igor Kushnir  ---
*** Bug 502827 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-02-16 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #19 from Igor Kushnir  ---
Heuristic disabling of auto-completion may be possible, but not necessarily
easy to implement. Also not a good long-term solution.

Perhaps finding the root cause and fixing the libclang bug is a better
investment of time. The bug appeared somewhere between Clang versions 16.06 and
17.06. One could examine git blame or git log of seemingly related files
looking for potential culprit commits. Or even bisect and find the commit that
introduced the regression, given a fast enough computer.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-02-16 Thread painless roaster
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #18 from painless roaster  ---
The bug has been around for a long time and is on a request to be placed in a
mental institution. Could you please make a workaround to not run the
background parser if you are cursor on a macro line?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-02-16 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #17 from Igor Kushnir  ---
*** Bug 500089 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-01-17 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #16 from Igor Kushnir  ---
*** Bug 498754 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2025-01-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=486932

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |HI

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2024-11-25 Thread David Murray
https://bugs.kde.org/show_bug.cgi?id=486932

David Murray  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2024-10-30 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #15 from Igor Kushnir  ---
*** Bug 495546 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2024-09-24 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #14 from Igor Kushnir  ---
(In reply to painless roaster from comment #13)
> is this it?
> 
> https://github.com/llvm/llvm-project/issues/105994 ?
Probably not. I don't think this KDevelop crash can be reproduced via a regular
compilation. The backtrace looks different.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2024-09-24 Thread painless roaster
https://bugs.kde.org/show_bug.cgi?id=486932

--- Comment #13 from painless roaster  ---
is this it?

https://github.com/llvm/llvm-project/issues/105994 ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing

2024-09-23 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=486932

Igor Kushnir  changed:

   What|Removed |Added

Summary|Background parser crash C++ |Crash when adding an
   |source  |#include statement during
   ||normal editing

-- 
You are receiving this mail because:
You are watching all bug changes.