VSCode editor is invoking cc1plus process every intellisense activation for gocv about gocv HOT 8 CLOSED

Hello @jcbritobr sounds like you are using Visual Studio code. I suggest setting the autobuild setting to false, as discussed here: microsoft/vscode-go#696 (comment)

The problem is that building the cgo code takes more time, hence the slowdown. Try setting "go.gocodeAutoBuild": false in your vscode settings.

Hope that helps!

from gocv.

Hi @deadprogram, good morning,

Setting "go.gocodeAutoBuild": false doesn't work. When you type any function of package, the cc1plus got high cpu and memory usage. Also the entire intellisense stop working. I will see if i fill a bug in vscode bug tracking, proper golang page:

Here is a cpu timeline snapshot of my machine:

from gocv.

This seems like an VS.CODE editor problem with Go packages that use cgo extensively, not something to do with GoCV itself. You might need to restart your editor, or ? I'm not really sure how to help you here.

from gocv.

Yes. I post only as a warning to this issue with gocode tooling. I will fill a bug in vscode or go tooling page, and use gocv with kate. Thank you for answare. Nice work with this package.

from gocv.

I appreciate you posting, since I actually was wondering why my own machine was doing this when editing code. I have almost exactly the same config as you do, VS code on Linux.

However my performance slowdown kicks in only occasionally, and it was when I make changes to the package itself, waiting for the updated golang tooling to update my workspace's "Problems" pane. When I turned off that setting, seems like have not had that problem. I was just examining my system monitor as well, and I did not see the spike you referred to.

from gocv.

I have a new machine and just installed the latest vscode. Seems like it is working more efficiently now? Perhaps it is my faster processor. Anyone else have any comments?

from gocv.

If you are consuming GoCV and not modifying it, using the go install instructions provided by @directive-cary in #63 addresses this. I will close this issue once the next release goes out.

from gocv.

These docs were released as part of v0.8.0 so now closing. Thanks again!

from gocv.