[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[bugzilla_noreply]

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

sla...@glamocanin.net changed:

   What|Removed |Added

 CC||sla...@glamocanin.net

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Kevin Funk]

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

--- Comment #14 from Kevin Funk  ---
Please continue commenting on the original report.

This one here is a different issue.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Fabian]

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

--- Comment #13 from Fabian  ---
https://bugs.kde.org/show_bug.cgi?id=369573 was my original bug report.
KDevelop still crashes every time I edit a js file on a remote server with
sftp://

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Fabian]

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

--- Comment #12 from Fabian  ---
Created attachment 104436
  --> https://bugs.kde.org/attachment.cgi?id=104436=edit
BT when KDevelop starts consuming memory

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Kevin Funk]

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

--- Comment #11 from Kevin Funk  ---
@Fabian: Same backtrace? Please post it here.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Fabian]

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

--- Comment #10 from Fabian  ---
This still happens to me in KDevelop 5.0.4.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DUPLICATE

--- Comment #9 from Kevin Funk  ---
Ah, interesting. This bug is probably related to bug 370495, which got resolved
in 5.0.2. This is the first time we see this issue happening on Linux I think.

Thanks for the feedback!

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

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Alexey Morozov]

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

Alexey Morozov  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Alexey Morozov  ---
The problem can't be reproduced in 5.0.2+ on the same test data in the same
environment (OS kernel and libs, amount of RAM etc). I guess, it was implicitly
resolved during the development.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||fab...@web2.0-apps.de

--- Comment #7 from Sven Brauch  ---
*** Bug 369573 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[via KDE Bugzilla]

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

walmartshop...@msn.com changed:

   What|Removed |Added

 CC||walmartshop...@msn.com

--- Comment #6 from walmartshop...@msn.com ---
I can reproduce this but only when opening a large javascript file from a
network share.  Opening the same file from a local drive is fine, but crashes
when opened from a smb:// or sftp:// location.

The following file causes the crash for me:

https://raw.githubusercontent.com/Mottie/tablesorter/master/dist/js/jquery.tablesorter.combined.js

Once the file is opened, the kdevelop process starts eating up a full CPU core
and consuming about 2GB of memory per second until it runs out of memory and
crashes.  It got up to 20GB of memory used before crashing.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Alexey Morozov via KDE Bugzilla]

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

--- Comment #5 from Alexey Morozov  ---
Started the `valgrind` process, but since it's working quite slowly (the
progress indicator reports only 1% of the project have been analyzed after
~hour of work), I expect things to complete at least a day after. Please don't
close the bug before :)

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Kevin Funk via KDE Bugzilla]

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

--- Comment #4 from Kevin Funk  ---
Can you try running KDevelop under valgrind? Thanks for helping out!

valgrind --smc-check=all-non-file --track-origins=yes kdevelop ...

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Alexey Morozov via KDE Bugzilla]

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

--- Comment #3 from Alexey Morozov  ---
... but certainly, I can run KDevelop under gdb and inspect variables on crash.
Also I can add some traces to KDevPlatform and recompile it, just give me
appropriate advices.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Alexey Morozov via KDE Bugzilla]

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

--- Comment #2 from Alexey Morozov  ---
No, unlikely. I have 16Gb of RAM and 8 gigs of swap, completely unused. Most of
RAM is used for file/buffer cache, according to `free -m`.

What's interesting is that removal of JS folder, loading the crippled project
into KDevelop and subsquent restoration of the folder with JS files solves the
problem: on the second run KDevelop discovers the new folder, and successfully
indexes JS files in it.

But nevertheless, there's plenty of RAM available, and nothing points to out of
memory errors (no swapping, no log messages from OOM killer, nothing). It could
be a problem with some other limits though. The project contains 1751 С++ files
and headers, and almost 13K of various JS files (mostly came from the
framework/libraries).

core file size  (blocks, -c) unlimited
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 63848
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 63848
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Unfortunately, the project isn't public, so I can't simply give an example.

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

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Kevin Funk via KDE Bugzilla]

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

--- Comment #1 from Kevin Funk  ---
Are you simply running out of memory? Is the project public, so we can try
reproduce the problem ourselves?

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