search

SeungukShin / cscope-code

Cscope Extension for Code
11 stars 4 forks source link

Scary number of processes #18

Open MahmoudYounes opened 1 year ago

MahmoudYounes commented 1 year ago

Building cscope.out invokes a massive number of processes. it also consumes a massive amount of memory causing other apps to be oom killed. I was wondering if there is a config/option that can be constraint/cap number of threads invoked.

Screenshot from 2023-07-26 23-05-10

lidaobing commented 7 months ago

similar problem on my project, sounds the query will trigger build, but build has no guard to prevent several build start together.

lidaobing commented 7 months ago

workaround for this problem:

  1. disable cscope-code plugin
  2. run cscope -RbU under the workspace dir
  3. re-enable cscope-code plugin
SeungukShin commented 7 months ago

You can avoid this problem by disabling auto generation of a cscope database in setting. I'll make a executing queue to fix this issue next version.

prateek-agrawal commented 3 months ago

Faced same issue , this generally happens when the workspace is huge.

  1. find . ( -path "./" -o -path "./tools" -o -path "./bootloader" -o -path "./output" -o -path "./buildroot" -o -path "./mk" -o -path "./kernel" -o -path "./dir_to_exclude3" ) -prune -o ( -name ".h" -o -name ".c" -o -name ".hpp" -o -name ".cpp" ) -print > cscope.files

use above command to exclude unnecessary directories and files inside those directories for the cscope to track.

  1. Run csope -bRkq
  2. It would make cscope faster as now it is not tracking unnecessary files and directories.