Re: BUG #3752: query yields "could not find block containing chunk", then server crashes

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Michael Charnoky <noky(at)nextbus(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3752: query yields "could not find block containing chunk", then server crashes
Date: 2007-11-16 09:52:54
Message-ID: 473D6876.3030405@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Charnoky wrote:

<snip>
>
> 2007-11-15 15:38:03.880 PST: ERROR: could not find block containing chunk
> 0x902fb98

This message appears in AllocSetFree or AllocSetRealloc function in
aset.c source. In both function it means that defined context does not
contain memory block. By my opinion there should be two more probable
scenarios:

1) memory block does not exist -> for AllocSetFree it means e.g. double
free or for AllocSetRealloc it means that somebody want to realloc
memory which was already freed.

2) memory is still allocated but in different context. However, palloc
and pfree should control it.

By my opinion it is double free problem, but without stack trace or
reproduction scenario it is difficult to find it.

Zdenek

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2007-11-16 11:08:49 Re: B-tree crash recovery error in 8.3 beta 2
Previous Message Zdenek Kotala 2007-11-16 08:29:43 Re: BUG #3752: query yields "could not find block containing chunk", then server crashes