[Computer-go] Strange GNU Go ladder behavior
drake at lclark.edu
Thu Jun 18 15:24:58 PDT 2015
I have no idea what GNU Go does for memory management, but that does offer
up a possibility: maybe the machine in question (a Google Compute Engine
instance) is running out of memory. I've been using the highcpu machine
types; I'll try a standard one (which has more memory) and see if the same
On Thu, Jun 18, 2015 at 1:41 PM, uurtamo . <uurtamo at gmail.com> wrote:
> What does it do for memory management? Is it ungracefully failing while
> evaluating the ladder itself due to ram issues?
> On Jun 18, 2015 12:15 PM, "Peter Drake" <drake at lclark.edu> wrote:
>> This list may not be able to help, but I'm running out of clues on this
>> I'm trying to run an experiment playing Orego against GNU Go in many
>> games. Some of the games don't end properly. As far as I can tell, here's
>> what happens:
>> 1) Orego plays out a losing ladder. (That needs to be fixed, but that's
>> another problem.)
>> 2) At some point in the ladder, GNU Go quietly dies without responding to
>> the move request.
>> Has anyone else encountered this?
>> Peter Drake
>> Computer-go mailing list
>> Computer-go at computer-go.org
> Computer-go mailing list
> Computer-go at computer-go.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Computer-go