From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Memory leak from ExecutorState context? |
Date: | 2023-03-01 18:09:44 |
Message-ID: | 20230301190944.56ed0665@karst |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 1 Mar 2023 18:48:40 +0100
Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> wrote:
...
> You'll find some intermediate stats I already collected in attachment:
>
> * break 1, 2 and 3 are from AllocSetAlloc, break 4 is from AllocSetFree.
> * most of the non-free'd chunk are allocated since the very beginning, before
> the 5000's allocation call for almost 1M call so far.
> * 3754 of them have a chunk->size of 0
> * it seems there's some buggy stats or data:
> # this one actually really comes from the gdb log
> 0x38a77b8: break=3 num=191 sz=4711441762604810240 (weird sz)
> # this one might be a bug in my script
> 0x2: break=2 num=945346 sz=2 (weird address)
> * ignoring the weird size requested during the 191st call, the total amount
> of non free'd memory is currently 5488MB
I forgot one stat. I don't know if this is expected, normal or not, but 53
chunks has been allocated on an existing address that was not free'd before.
Regards,
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2023-03-01 18:09:53 | Re: add PROCESS_MAIN to VACUUM |
Previous Message | Melanie Plageman | 2023-03-01 17:51:16 | Add pg_walinspect function with block info columns |