Memory leak libapache2-mod-auth-pgsql
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libapache2-mod-auth-pgsql (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libapache2-
I have web site (with apache2) and when I use a pgsql authentification to access it, I can see a (huge) memory leak.
I use libapache2-
Repport of "valgrind --leak-check=full --show-
"""
==14493== 97,020,716 bytes in 2,228 blocks are indirectly lost in loss record 14 of 14
==14493== at 0x4022765: malloc (vg_replace_
==14493== by 0x4557C9D: (within /usr/lib/
==14493== by 0x455831E: CRYPTO_malloc (in /usr/lib/
==14493== by 0x461A587: (within /usr/lib/
==14493== by 0x461A1BA: COMP_CTX_new (in /usr/lib/
==14493== by 0x44FBFAA: tls1_change_
==14493== by 0x44F3632: ssl3_connect (in /usr/lib/
==14493== by 0x4505399: SSL_connect (in /usr/lib/
==14493== by 0x41EBFC3: (within /usr/lib/
==14493== by 0x41DDA1F: PQconnectPoll (in /usr/lib/
==14493== by 0x41DE7AE: (within /usr/lib/
==14493== by 0x41E0081: PQsetdbLogin (in /usr/lib/
==14493==
==14493== LEAK SUMMARY:
==14493== definitely lost: 134,540 bytes in 338 blocks.
==14493== indirectly lost: 97,022,457 bytes in 2,258 blocks.
==14493== possibly lost: 9,448,400 bytes in 163 blocks.
==14493== still reachable: 1,614,260 bytes in 1,957 blocks.
==14493== suppressed: 0 bytes in 0 blocks.
"""
Hi,
It looks like this bug could be a duplicate of Bug #224945, which actually points to SSL.
Would it be possible for you to retry this use case without using SSL? That would help narrow the issue to libssl, rather than libapache2- mod-auth- pgsql.
Thanks,
:-Dustin