[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Go - deadlocked processes causing memory leaks
The simplest response is to, upon timeout, attach a sink to the response channel to ensure that the result is able to be cleaned up. If you ask a process (whether transient or not) to do something and then communicate it to you, it it reasonable to accept the responsibility for ensuring that it's actually done.
In the short-term you'd have two goroutines that are blocked waiting for each other, but as long as the Get() is guaranteed to return you should be okay.Â
On Sun, 29 Mar 2015 at 16:19 Rick Beton <rick.beton@xxxxxxxxx
"Because the channel is non-blocking, ..."
"Because the channel is unbuffered, ..."
(edited version follows below)