--- 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

    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.

Reply via email to