From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from x230.inri ([199.241.189.110]) by ttr; Mon Feb 24 00:58:20 EST 2014
Date: Mon, 24 Feb 2014 00:58:12 -0500
From: sl@9front.org
To: 9front@9front.org
Subject: no image after reclaim
Message-ID: <99013c63f63808ca066ed0c715e6eec7@x230.inri>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: ISO-certified leveraged just-in-time high-performance manager
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

A while back I wrote an rss feed reader in go (the
parser is a pre-existing library, which is the reason
I chose to write the program in go)[0]. This runs twice
an hour on my cpu server, instigated by cron.

Result:

Every day or two my cpu server locks up. Remote sessions
stall. The console stops responding to keys being pressed on
the keyboard. The console screen fills up with this message,
repeated over and over:

no image after reclaim

The error message seems to be triggered in
/sys/src/9/port/segment.c.

I never had this problem before I started running my
go program. The problem first appeared around the
same time I started running my go program. I'm not sure
if I'm doing something stupid in my program, if something
is wrong with the go runtime, if something is wrong with
the 9front kernel, or some combination of the above.

sl

[0] http://code.google.com/p/rrss