News for hackers. Stuff that matters.
Re:On the Road to Pure Go X11 GUIs by antaviana on Friday September 07, 2018 @04:54PM (#17937552)
I wrote my first Go application that was to be run on a very Linux instance (1 GB), serving results to HTML from an in-memory map of some 150MB. The memory growth was really out of control, panicking with "out of memory" under even low load until I added debug.FreeOSMemory after serving each search result. Even with that, I had to change the instance to 2GB. It was a one-off excperiment, but I missed releasing memory by myself to ensure a manageable working set.
Re:On the Road to Pure Go X11 GUIs by sagichmal on Friday September 07, 2018 @06:03PM (#17937997)
Your program certainly had a bug. Feel free to paste a link to it here, I may be able to debug it.
Re:On the Road to Pure Go X11 GUIs by courtf on Friday September 07, 2018 @06:19PM (#17938093)
Yeah definitely a bug.

I've worked on systems that allocated and freed hundreds of GB every 10 minutes, written in Go with no such issues.

Re:On the Road to Pure Go X11 GUIs by justinclift on Friday September 07, 2018 @06:41PM (#17938218)
Is the code online somewhere?

It really sounds like there was something not-quite-right in there. Might not be too hard for someone with time + clue to spot it. :)

Re:On the Road to Pure Go X11 GUIs by dcu on Saturday September 08, 2018 @09:49AM (#17940791)
that's called a memory leak: https://en.wikipedia.org/wiki/Memory_leak

I've seen happening in Go multiple times when people forget to close the response body after making a http request.