https://bugs.kde.org/show_bug.cgi?id=379551
Martin Fuhrer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #33 from Milian Wolff ---
It could potentially be the same reason as the one explained here:
https://codereview.qt-project.org/#/c/218906/
i.e. for some reason clang crashes, then we essentially leak memory...
--
You
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #32 from Martin Fuhrer ---
Hi Milian, thanks for the heaptrack fix. It appears to be working correctly
now. I encountered the memory leak again this morning (workstation started
freezing up), and tried to quit
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #31 from Martin Fuhrer ---
Created attachment 112318
--> https://bugs.kde.org/attachment.cgi?id=112318=edit
KDevelop backtrace (PID 16665)
Backtrace generated when I tried to quit KDevelop during memory leak.
https://bugs.kde.org/show_bug.cgi?id=379551
Martin Fuhrer changed:
What|Removed |Added
Attachment #111039|0 |1
is
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #29 from Milian Wolff ---
ok Martin, heaptrack should now work properly! please try again. and thanks a
lot for the report, this was quite a nasty issue!
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=379551
Milian Wolff changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #27 from Milian Wolff ---
You can try `heaptrack_print heaptrack.*.gz |& less` - it's CLI only and
doesn't depend on any KF5 libs.
The commands look harmless, I wonder what the issue is here...
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #26 from Martin Fuhrer ---
Strange, heaptrack was running the kdevelop session for around eight hours (and
kdevelop was running smoothly for most of this time, using a stable amount of
memory when I checked a
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #25 from Milian Wolff ---
Martin, how did you run heaptrack? The track file only sees 27.7MB and it only
recorded for 9.7 seconds. Did it really only run for such a short time?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #24 from Martin Fuhrer ---
I have been testing the KDevelop 5.2.1 AppImage on Debian 7.8 (wheezy) for the
last few weeks (our office is still using KDevelop 4.7.4, which runs great,
albeit a bit slow with large
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #23 from Martin Fuhrer ---
Created attachment 112099
--> https://bugs.kde.org/attachment.cgi?id=112099=edit
KDevelop log (PID 12200)
First and last 1000 lines (full log is 45 MB)
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=379551
Martin Fuhrer changed:
What|Removed |Added
Attachment #105746|0 |1
is
https://bugs.kde.org/show_bug.cgi?id=379551
Martin Fuhrer changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=379551
ddz changed:
What|Removed |Added
Attachment #110818|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #20 from ddz ---
Hi,
I don't see any "crash" keywords in terminal.
Also, I found if I did the "clear cache" when launch kdevelop.
Even run 10+ hours, the max memory usage VIRT 8922M, RES 3493M, SHR 32440
At
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #19 from ddz ---
Hi,
I don't see any "crash" keywords in terminal.
Also, I found if I did the "clear cache" when launch kdevelop.
Even run 10+ hours, the max memory usage VIRT 8922M, RES 3493M, SHR 32440
At
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #18 from Milian Wolff ---
Hey there,
I was just notified about this:
https://codereview.qt-project.org/#/c/218906/
So maybe that's the issue you are facing. Do you see messages about crashes on
the command line output?
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #17 from ddz ---
I will try it. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #16 from Milian Wolff ---
That file is equally uninteresting and also only shows deflate stuff. Heaptrack
only saw a memory peak of 2.7 *mega*byte, so I guess attaching heaptrack to the
AppImage really doesn't work at
https://bugs.kde.org/show_bug.cgi?id=379551
ddz changed:
What|Removed |Added
Version|5.1.0 |5.2.1
--- Comment #15 from ddz
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #14 from ddz ---
Created attachment 110872
--> https://bugs.kde.org/attachment.cgi?id=110872=edit
after_click_close_btn
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #13 from ddz ---
Created attachment 110871
--> https://bugs.kde.org/attachment.cgi?id=110871=edit
htop(2018-02-21)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #12 from ddz ---
Created attachment 110870
--> https://bugs.kde.org/attachment.cgi?id=110870=edit
heaptrack(2018-02-21)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #11 from ddz ---
It's happened today, I just open the kdevelop and left it there.
Several hours later, I come back my desk, try to do something.
I feel my computer have a little freeze (cursor will stuck a few
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #10 from ddz ---
Also, I build heaptrack from this commit
https://github.com/KDE/heaptrack/commit/6e31841708b351b9f53e59d384e94df014d927ed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #9 from ddz ---
Hi, I am sorry, the htop screenshot and the heaptrack not create at the same
time.
I am keep running heaptrack with kdevelop today, but seem not happened today.
(Maybe I cleaned the cache, when I
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #8 from Milian Wolff ---
that heaptrack trace is pretty meaningless - it only shows stuff in deflate and
not a lot of memory consumption in total. Are you sure the pid it attached to
is the one you saw in htop? Also, just
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #7 from ddz ---
Hi, I have the same issue.
My system info is
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.3 (stretch)
Release:9.3
Codename: stretch
Linux
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #6 from ddz ---
Created attachment 110819
--> https://bugs.kde.org/attachment.cgi?id=110819=edit
heaptrack(2018-02-20)
heaptrack.kdevelop.17748.gz
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=379551
ddz changed:
What|Removed |Added
CC||blazingfore...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #4 from Milian Wolff ---
The way AppImage works makes it impossible to track kdevelop with heaptrack
currently. So you'll either have to runtime attach heaptrack later on
(heaptrack --pid $(pidof kdevelop), assuming an
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #3 from Manvydas Šliamka ---
I'm really sorry for not replying sooner, but the defense of my Master's thesis
is soon and I just do not have the time to experiment with KDevelop
extensively.
First of all - tabs. I
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #2 from Manvydas Šliamka ---
Created attachment 105746
--> https://bugs.kde.org/attachment.cgi?id=105746=edit
Heaptrack results
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379551
Milian Wolff changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
35 matches
Mail list logo