roxma / nvim-completion-manager

:warning: PLEASE USE https://github.com/ncm2/ncm2 INSTEAD
MIT License
917 stars 49 forks source link

High resource consumption #147

Closed zackhsi closed 6 years ago

zackhsi commented 6 years ago

The python completer is using a full core. This happened after waking my laptop in the morning.

screen shot 2017-10-17 at 8 42 54 am

dtruss shows the syscall count as:

CALL                                        COUNT
munmap                                         86
mmap                                          131

I recorded a trace via Instruments, but didn't get anything new out of it.

Any ideas what could have caused this? During normal operation, this does not happen.

roxma commented 6 years ago

Similar issue #62

I believe this is upstream issue. // cc @davidhalter

That's why only jedi source is running as a standalone process.

Maybe we need more workarounds. Like auto restarting the process when there's no edit activity for a while.

roxma commented 6 years ago

// cc @theFool32

davidhalter commented 6 years ago

There might still be issues in jedi 0.11.0, I'm not sure. If you can reproduce it, please open an issue. This was definitely an issue in 0.10.2, so if your jedi version is that old, please upgrade.

zackhsi commented 6 years ago

Can't repro. Will update if that becomes the case.