[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=367893

pyrk...@go2.pl changed:

   What|Removed |Added

 CC||pyrk...@go2.pl

--- Comment #6 from pyrk...@go2.pl ---
Yes, disabling background parsing allows me to open remote js files without any
problem.

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Martin Riethmayer]

https://bugs.kde.org/show_bug.cgi?id=367893

Martin Riethmayer  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Martin Riethmayer  ---
This is most likely a duplicate of 
https://bugs.kde.org/show_bug.cgi?id=369573
as this also happens for me on remote file systems only. I'll try to provide a
heaptrack at the other report.

Sorry for the delayed reply.

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

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

--- Comment #4 from Milian Wolff  ---
Oh, and you could also try out heaptrack with the project you can reproduce the
issue with:


heaptrack kdevelop -s ...
# wait a few seconds while verifying that the process is actually exhibiting
the bad behavior
# ctrl + C to quit, alternatively use `ulimit -v` to set some limit on the
virtual memory to prevent
# it from taking down your other applications

then send us the heaptrack.gz data file, e.g. upload it here

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

--- Comment #3 from Milian Wolff  ---
I cannot reproduce this with the attached file. Can you try to create a MWE
with a tarball of a project I can open in KDevelop?

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Martin Riethmayer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

--- Comment #2 from Martin Riethmayer  ---
Created attachment 101107
  --> https://bugs.kde.org/attachment.cgi?id=101107=edit
Loading this file with background parser enabled crashes KDevelop for me

Sorry for the late reply, I was now able to reproduce the issue, I've attached
the file that is causing the freeze / crash. 
As soon as I open that file, KDevelopkdev increases its memory usage from ca
100MB to 14.6 GB (which is probably the maximum available at that time) if the
background parser is active. If I deactivate the background parser, everything
is working as expected.

This is on KDevelop 5.0.0, KDE FW 5.25.0, Qt 5.6.1, KDE-Plasma 5.74, Kernel
4.7.2-1-default, 64-bit xcb windowing system, Intel Core i7-4770R CPU@3.2 GHz,
16 GB RAM.

Two more observations: 
If I open the file with disabled background parser, then enable the parser and
immediately quit KDevelop (CTRL+Q), the application window disappears, but the
process is still active and will grab all RAM until it crashes. You can
actually watch the RAM usage go up in the system monitor.
After KDevelop crashes, there's usually (but not every time) still some kind of
zombie-process in the system monitor.

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Milian Wolff  ---
 "stutter" and backtrace looks like you ran out of memory, leading to swapping
and eventually OOM probably. could that be the case?

what project are you trying to load - can we try to reproduce and see how it
performs for us? maybe it's exhibiting some bad behavior somewhere in our code
and we could optimize that. but with just this backtrace, there's not much we
can do, I'm afraid to say

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

[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background

[Aleix Pol via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367893

Aleix Pol  changed:

   What|Removed |Added

  Component|general |Language Support:
   ||QML/JavaScript
 CC||aleix...@kde.org

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