[haiku-commits] Re: haiku: hrev43358 - src/servers/app/stackandtile

  • From: Ingo Weinhold <ingo_weinhold@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 29 Nov 2011 17:47:21 +0100

On 2011-11-28 at 22:50:13 [+0100], Clemens <clemens.zeidler@xxxxxxxxxxxxxx> 
wrote:
> On Tue, 29 Nov 2011 10:33:01 +1300, <clemens.zeidler@xxxxxxxxxxxxxx> wrote:
> 
> > Revision:    hrev43358
> > Commit:      d240743e9be7d720aadedd5a0185a61a907bca74
> > URL:         http://cgit.haiku-os.org/haiku/commit/?id=d240743
> > Author:      czeidler <haiku@xxxxxxxxxxxxxxxxxx>
> > Date:        Mon Nov 28 21:30:42 2011 UTC
> >
> > Ticket:      https://dev.haiku-os.org/ticket/8103
> >
> > - The SATGroup has been deleted to early, that probably causes #8103.
> > Holding a reference on the WindowArea (which hold a ref to the group)
> > extends the lifetime till we are done.
> > - Fix some stayBelowMouse flags.
> 
> Actually I was not able to reproduce the bug consistently. Also when I
> explicit called the deleted object. What happen internally? is the memory
> still valid for a short time?

It is very unlikely that freeing a small allocation causes the area to be 
deleted or shrunk, so the memory range will very likely remain valid. 
Whether the memory is overwritten is another matter. I believe by default 
our allocator doesn't overwrite the memory (save for a free list link 
somewhere maybe) -- you'd have to use the debug libroot to make sure of that 
-- so it mostly depends on whether someone else is allocating and 
overwriting that memory afterwards.

CU, Ingo

Other related posts: