On Tue, Jan 07, 2014 at 08:37:27PM +0200, Noel Maersk wrote:
> On 06/01/14 16:33, Noel Maersk wrote:
> > Around new year I started catching a sporadic segfault from
> > obworker. I didn't save the backtraces (that's what drunkedness does
> > :/), and can't determine what triggers it and how to reproduce (yet).
> >
> ...
>
> OK, found it.
>
> After running for some time (hours), obworker takes up all memory and
> gets terminated.
>
> There are sometimes streaks of these:
>
> > ...
> > ERROR [poller]: Storing block
> > 000000000000001e4a1dba552d7a60d5dc649185d04521c9f5516a270f1bb7f8:
> > Matching previous object found
> > ...
>
> ...

P.S. Once the blockchain is fully up-to-date, this is no longer present.