Open nocaway opened 5 years ago
I didn't find yb_bit.sql in the source code. @nocaway Do you mind pointing me where I can find the file ?
I was tracing the leak reported in the first hunk above:
#6 0x53bf59 in PSQLexec /net/centos-gcp-cloud-jenkins-slave-71b/share/jenkins/workspace/yugabyte-phabricator@4/src/postgres/src/bin/psql/../../../../../../src/postgres/src/bin/psql/common.c:721:8
which, at the time of creation of this issue, called PQexecFinish
.
Nowadays, I couldn't find PQexecFinish
in the whole of common.c
Actually the above observation applies to both reported leaks because both involve PQexecFinish
.
I have examined git log around libpq/fe-exec.c and related files to see if there has been some leak fix upstream.
There was none in PG 11 branch which we don't already have.
@m-iancu Was this a legitimate memory leak, in the product? Is this lower pri, as it only affects the PG backend that the user is connected to?
Jira Link: DB-1257 Reproducible case: Uncomment '\d' command at the end of test file "yb_bit.sql" and run the test with ASAN build.
Symptoms ASAN reported memory leaks in psql when '\d' - describe command - is used. This occurs in PG 11 but not PG 10. Af the first glance, the leaking callstack showed the issue was in client application such as "psql"