Summary: | kdevelop crashes while parsing javascript files | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Alexey Morozov <morozov> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | fabian, slavko, walmartshopper |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | BT when KDevelop starts consuming memory |
Description
Alexey Morozov
2016-09-22 07:04:35 UTC
Are you simply running out of memory? Is the project public, so we can try reproduce the problem ourselves? 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. ... 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. Can you try running KDevelop under valgrind? Thanks for helping out! valgrind --smc-check=all-non-file --track-origins=yes kdevelop ... 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 :) 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. *** Bug 369573 has been marked as a duplicate of this bug. *** 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. 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 *** This still happens to me in KDevelop 5.0.4. @Fabian: Same backtrace? Please post it here. Created attachment 104436 [details]
BT when KDevelop starts consuming memory
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:// Please continue commenting on the original report. This one here is a different issue. |