[Linux-HA] Potential memory leak

[Pavol Gono]

I tried sources from revision 10054 (code equivalent to 10057)
hg clone -r10054 http://hg.linux-ha.org/dev
and I saw the message of pengine again.
So it wasn't fixed...

Palo


On 1/29/07, Andrew Beekhof <beekhof at gmail.com> wrote:
> On 1/29/07, Pavol Gono <palo.gono at gmail.com> wrote:
> > Hi
> >
> > I have seen the memory leak messages also when using stable code
> > (2.0.8 with minor modifications). Is it possible to identify, which
> > changeset fixed the leaks?
>
> I'd recommend "hg bisect"
>
> >
> > Palo
> >
> >
> > On 1/23/07, Andrew Beekhof <beekhof at gmail.com> wrote:
> > > On 1/23/07, Pavol Gono <palo.gono at gmail.com> wrote:
> > > > On 1/23/07, Andrew Beekhof <beekhof at gmail.com> wrote:
> > > > > On 1/23/07, Pavol Gono <palo.gono at gmail.com> wrote:
> > > > > > Hi
> > > > > >
> > > > > > Are these messages anything, what should I worry about?
> > > > >
> > > > > I dont know about "worry", but I appreciate you reporting it.
> > > > >
> > > > > Can you attach /var/lib/heartbeat/pengine/pe-input-900.bz2 on the
> > > > > machine you sent the logs from?
> > > >
> > > > attached
> > > >
> > > > I'll post new thread with another topic soon, you can find another
> > > > such message inside.
> > >
> > > whatever it is, by rev 10057 it seems to be gone.
> > >
> > > >
> > > > >
> > > > > > pengine[24269]: 2007/01/23_01:39:36 WARN: crm_mem_stats: Potential
> > > > > > memory leak detected: 3770 alloc's vs. 3769 free's (1) (52 bytes
> not
> > > > > > freed: req=205, alloc'd=0)
> > > > > > pengine[24269]: 2007/01/23_01:39:36 WARN: process_pe_message:
> Unfree'd
> > > > > memory
> > > > > >
> > > > > > This happened after 7 hours of intensive testing on 2-node
> cluster.
> > > > > > Failovers are triggered every minute. http://hg.linux-ha.org/dev/,
> rev
> > > > > > 10038.
> > > > > > I saw such message only once so far.
> > > > > >
> > > > > > Palo
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Linux-HA mailing list
> > > > > > Linux-HA at lists.linux-ha.org
> > > > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > > > > > See also: http://linux-ha.org/ReportingProblems
> > > > > >
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > Linux-HA mailing list
> > > > > Linux-HA at lists.linux-ha.org
> > > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > > > > See also: http://linux-ha.org/ReportingProblems
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Linux-HA mailing list
> > > > Linux-HA at lists.linux-ha.org
> > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > > > See also: http://linux-ha.org/ReportingProblems
> > > >
> > > >
> > > >
> > > _______________________________________________
> > > Linux-HA mailing list
> > > Linux-HA at lists.linux-ha.org
> > > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > > See also: http://linux-ha.org/ReportingProblems
> > >
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA at lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>