Re: Probable memory leak with ECPG and AIX

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, "Dr(dot) Michael Meskes" <michael(dot)meskes(at)credativ(dot)com>
Subject: Re: Probable memory leak with ECPG and AIX
Date: 2021-12-11 07:49:25
Message-ID: CAECtzeXYvZwNUprdE2FTGmM9MG67vzdG9MOpnaYZw6fhk1j3=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le sam. 11 déc. 2021 à 07:52, Justin Pryzby <pryzby(at)telsasoft(dot)com> a écrit :

> On Fri, Dec 10, 2021 at 03:40:50PM +0100, Guillaume Lelarge wrote:
> > Hello,
> >
> > Our customer thinks he has found a memory leak on ECPG and AIX.
> >
> > The code is quite simple. It declares a cursor, opens it, and fetches the
> > only line available in the table many times. After some time, the client
> > crashes with a segfault error. According to him, it consumed around
> 256MB.
> > What's weird is that it works great on Linux, but crashed on AIX. One
> > coworker thought it could be the compiler. Our customer used cc, but he
> > also tried with gcc, and got the same error.
>
> A memory leak isn't the same as a segfault (although I don't know how AIX
> responds to OOM).
>
> Can you show that it's a memory leak ? Show RAM use increasing
> continuously
> and linearly with loop count.
>
> How many loops does it take to crash ?
>
> Could you obtain a backtrace ?
>
>
Thanks. I'll try to get all these informations, but it won't be before
monday.

--
Guillaume.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-12-11 13:12:55 Re: isolationtester: add session name to application name
Previous Message Justin Pryzby 2021-12-11 06:52:36 Re: Probable memory leak with ECPG and AIX