5 ms·
Do you know if the memory leak still exists on 64-bit? I wasn't able to determine that. I've read that the solution is to use 64-bit, but I don't know if that r
by genwin 14y ago
Do you know if the memory leak still exists on 64-bit? I wasn't able to determine that. I've read that the solution is to use 64-bit, but I don't know if that really just means that a 64-bit system will take the memory leak far longer to crash it.
I'm not too concerned about the attitude of some Golang devs (they are volunteers, after all), but I am very concerned about any memory leak or other serious bug that won't be fixed for a year+.
- thebluesky 14y agoMy understanding is that they are mostly Google employees rather than volunteers. Go uses a conservative GC which means that the probability of a leak is much lower on a 64 bit system rather than that a 64 bit system has more headroom to leak before it crashes.
- genwin 14y agoThanks for that simple explanation. My use case is fine with 64-bit only, so I'll proceed with Golang. I would probably decline if I needed to support 32-bit, given how nasty memory leaks are.
- enneff 14y ago64-bit systems have so much more address space that the issue will never manifest on 64-bit systems. At least, not in the next 100 years.
- thebluesky 14y agoPlease make a plan about official binaries for RHEL/CentOS 5. Yes it's an old kernel, but it's still used heavily by many organizations.
- deleted 14y ago[deleted]