Алексей
Алексей
To isolate the problem, the provided code uses randomly generated images instead of actual screen captures.
Thanks for the quick reply! I've applied the optimizations you suggest, but as far as I can tell, the problem persists. Please see this screenshot:  `HeapAlloc` indeed...
Neither intentionally, nor otherwise: ``` >SET | grep -i -e "^go" GOPATH=C:\Users\user\go ```
I also tried running `runtime.GC()` manually on each cycle, was of no use.
This is awesome! Now memory usage is stable, at least for me and this particular test case. Thanks a lot @roblillack ❤️