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

https://bugs.kde.org/show_bug.cgi?id=369182 sla...@glamocanin.net changed: What|Removed |Added CC||sla...@glamocanin.net -- You are

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

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

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:

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

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

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

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

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

https://bugs.kde.org/show_bug.cgi?id=369182 Kevin Funk changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE --- Comment #9 from

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

https://bugs.kde.org/show_bug.cgi?id=369182 Alexey Morozov changed: What|Removed |Added Resolution|--- |WORKSFORME

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

https://bugs.kde.org/show_bug.cgi?id=369182 Sven Brauch changed: What|Removed |Added CC||fab...@web2.0-apps.de ---

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

https://bugs.kde.org/show_bug.cgi?id=369182 walmartshop...@msn.com changed: What|Removed |Added CC||walmartshop...@msn.com --- Comment #6

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

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

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

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

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

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

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

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,

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

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.