Gregory's Server@Gargron I would start by debugging all the lilliput library bits. (which is C based and probably not a straight Go problem)
Probably separate and hardcode all the lilliput operations until you make sure those work, and then integrate them into your main server programme when those bits are ready.
|
Top-level
@h
No comments
|
@haitch The program works! It does what it's supposed to do. It just leaks memory while doing it.
I think the sync.Pool approach might not be working well. What I need is to allocate a fixed number of ImageOps objects and then use them from the handler in a thread-safe way. I don't know how to do that in Go, however.
What also gives me pause is how the bytes of the image are passed around. I feel like there might be more efficient methods of doing it