Skip to content
This repository was archived by the owner on Oct 12, 2022. It is now read-only.

There may be a memory leak? #208

Closed
KISSMonX opened this issue Oct 20, 2017 · 8 comments
Closed

There may be a memory leak? #208

KISSMonX opened this issue Oct 20, 2017 · 8 comments

Comments

@KISSMonX
Copy link

cc859af8-2b72-4be2-8bee-7510fdbe2e1d

@keegancsmith
Copy link
Member

@KISSMonX Could you update your go langserver? This is likely a duplicate of the now fixed issue #178

@leaxoy
Copy link

leaxoy commented Oct 20, 2017

This extension looks unavailable, there is my config: -usebinarypkgcache=false -trace, after a while, memory usage increase crazy, then will be killed by system.

@leaxoy
Copy link

leaxoy commented Oct 20, 2017

Is there any way for user to debug this extension, maybe I can provide more log with debug info

@emidoots
Copy link
Member

emidoots commented Oct 20, 2017 via email

@leaxoy
Copy link

leaxoy commented Oct 20, 2017

Ohh, but without this option for some package the hover info is missing.

@leaxoy
Copy link

leaxoy commented Oct 20, 2017

Looks as if during my type sending contentChanges event, memory increase crazy.

@keegancsmith
Copy link
Member

We don't support using that option in a desktop environment. It is used in our server environment where the working copy is immutable and type information is shared between different working copies.

If you do not have memory issues without the flag, are you happy to close this and file an issue for the missing hover info?

@leaxoy
Copy link

leaxoy commented Oct 20, 2017

Sure, thank you! However, this issue isn't open by me 🤪

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants