3 ms·

We have support chat on our website, if you can go there i can help you debug the problem. Thanks.

• grosskur 13y ago
  I'm also seeing this on a 512MB DigitalOcean server. From previous experience, I'm pretty sure the problem is that when you compile with Go 1.1 your program's VM commit charge is much larger (~500M) than it was with Go 1.0 (~70M): https://code.google.com/p/go/issues/detail?id=5236 https://code.google.com/p/go/issues/detail?id=5236 Hence it runs out of memory on low-memory systems. Rebuild Go 1.1 from source with this patch applied: https://codereview.appspot.com/download/issue9791044_36001.diff https://codereview.appspot.com/download/issue9791044_36001.d... Then rebuild your program and it should be fixed.
  • jshahid 13y ago
    Did you turn off overcommitting ? also which distro and cpu architecture are you using ?
    • grosskur 13y ago
      No, overcommit is turned on (overcommit_memory=0, overcommit_ratio=50). Ubuntu 12.04.3 x86_64, kernel 3.8.0-29-generic.
• tlongren 13y ago
  Where's this support chat? I can't find it for the life of me on getanomalous.com.