[kdevelop] [Bug 472669] CPU usage goes to 100% after closing the KDevelop window

2023-07-26 Thread Igor Kushnir 
https://bugs.kde.org/show_bug.cgi?id=472669

Igor Kushnir  changed:

   What|Removed |Added

 CC||igor...@gmail.com
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WORKSFORME

--- Comment #1 from Igor Kushnir  ---
How long did you wait for KDevelop to exit? KDevelop has to save background
parsing results on disk, which can take minutes after a long background
parsing.

If KDevelop keeps hanging for a long time, please run the following command
(replace "12345" with the hanging kdevelop process ID):
gdb -batch -ex "thread apply all bt" -ex "quit" -p 12345 >
~/kdevelop-freeze-on-exit.bt
(in case of a "ptrace: Operation not permitted." error, follow an advice in
https://userbase.kde.org/KDevelop5/Manual/Debugging_programs#Attaching_the_debugger_to_a_running_process)
Then post the contents of the file ~/kdevelop-freeze-on-exit.bt here.

A workaround that is likely to help (possibly temporarily) is to clear the
cache when the "Session Crashed -- KDevelop" dialog appears.

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

[kdevelop] [Bug 472669] CPU usage goes to 100% after closing the KDevelop window

2023-07-27 Thread JStrebel 
https://bugs.kde.org/show_bug.cgi?id=472669

--- Comment #2 from JStrebel  ---
I exited KDevelop and after waiting 10 minutes, the kdevelop process is still
using 100% CPU. So I don't think the kdevelop process is doing anything
meaningful.

Clearing the cache using 
jstrebel@phoenix:~> CLEAR_DUCHAIN_DIR=1 kdevelop
OR
deleting the directories ~/.cache/kdevelop and kdevduchain
did not change the faulty behaviour.

Here is the contents of the file kdevelop-freeze-on-exit.bt:
[New LWP 1970]
[New LWP 1971]
[New LWP 1972]
[New LWP 1977]
[New LWP 1979]
[New LWP 1985]
[New LWP 1986]
[New LWP 2007]
[New LWP 2092]
[New LWP 2123]
[New LWP 2126]
[New LWP 2127]
[New LWP 2128]
[New LWP 2129]
[New LWP 2130]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x7f46146f98ca in ?? () from /usr/lib64/libKDevPlatformLanguage.so.57

Thread 16 (Thread 0x7f457e7fc700 (LWP 2130) "Queue(0x55dfa86"):
#0  0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f4615f0f19b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f460cde7feb in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() from /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f460cde6650 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f460cde6f1b in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f4615f088bc in ?? () from /usr/lib64/libQt5Core.so.5
#11 0x7f460e93c6ea in start_thread () from /lib64/libpthread.so.0
#12 0x7f461592749f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f457effd700 (LWP 2129) "Queue(0x55dfa86"):
#0  0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f4615f0f19b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f460cde7feb in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() from /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f460cde6650 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f460cde6f1b in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f4615f088bc in ?? () from /usr/lib64/libQt5Core.so.5
#11 0x7f460e93c6ea in start_thread () from /lib64/libpthread.so.0
#12 0x7f461592749f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f457f7fe700 (LWP 2128) "Queue(0x55dfa86"):
#0  0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f4615f0f19b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f460cde7feb in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() from /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f460cde6650 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f460cde7f0d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f460cde6f1b in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f4615f088bc in ?? () from /usr/lib64/libQt5Core.so.5
#11 0x7f460e93c6ea in start_thread () from /lib64/libpthread.so.0
#12 0x7f461592749f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f457700 (LWP 2127) "Queue(0x55dfa86"):
#0  0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f4615f0f19

[kdevelop] [Bug 472669] CPU usage goes to 100% after closing the KDevelop window

2023-07-27 Thread Igor Kushnir 
https://bugs.kde.org/show_bug.cgi?id=472669

Igor Kushnir  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Igor Kushnir  ---
Looks like a duplicate of a long-standing issue, which I have (almost?) never
experienced myself. One more workaround you could try is creating a new session
via `kdevelop -n test-session`.

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

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