Memory leak?

[anton19286]

for i:=0; i<40000; i++ {
c, _ := xgb.NewConn()
time.Sleep(10*time.Microsecond)
c.Close()
}
produce 1.5 G of allocation

[BurntSushi]

Might be. I think at least two goroutines (generateXIds and generateSeqIds) from each connection will never quit.

Out of curiosity, why are you creating so many connections?

[anton19286]

I tried to use vova616/screenshot for VNC server.
It creats and closes new connection on every call.

[BurntSushi]

That library should probably expose a way to reuse a connection. Nevertheless, we shouldn't leak goroutines either. :-)

[4nte]

I'm using https://github.com/kbinani/screenshot which depends on this library.
Everytime this library captures the screen, it creates and closes a new connection - which over time fills the entire memory and crashes.

[jezek]

@4nte There is a PR #44, which also fixes this issue. I have forked this repo, applied the fix and using it in my projects successfully. Maybe it helps.

If it helps, write it here, maybe it helps to persuade the maintainer to merge the PR.

Side note: There is also a PR #45, which adds some more tests and leakage tests.

[4nte]

@4nte There is a PR #44, which also fixes this issue. I have forked this repo, applied the fix and using it in my projects successfully. Maybe it helps.

If it helps, write it here, maybe it helps to persuade the maintainer to merge the PR.

Side note: There is also a PR #45, which adds some more tests and leakage tests.

I will rewrite https://github.com/kbinani/screenshot to use your fork and test it.
If it fixes the problem I'll open a PR for kbinani/screenshot to use your fork instead since this issue is pretty old.