BUG #16348: Memory leak when parsing config

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: hghwng(at)gmail(dot)com
Subject: BUG #16348: Memory leak when parsing config
Date: 2020-04-07 13:36:20
Message-ID: 16348-018c10b6fd16ebcc@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16348
Logged by: Hugh Wang
Email address: hghwng(at)gmail(dot)com
PostgreSQL version: 12.2
Operating system: Arch Linux
Description:

SUMMARY:
Memory leaked by gui-file.l:ProcessConfig accumulates across repeated SIGHUP
cycles.

ANALYSIS:
When parsing config file, gui-file.l:ProcessConfig sets up memory context.
It invokes guc-file.l:ProcessConfigFileInternal, which is expected to leak
memory. It's okay because the leaked memory will be freed when cleaning up
the context. Next, guc-file.l:ProcessConfigFileInternal associates each
config item with filename by calling guc.c:set_config_option, which calls
guc.c:guc_strdup. However, guc.c:guc_strdup is not aware of the memory
context, and invokes libc.so:strdup directly.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Masahiko Sawada 2020-04-07 14:35:16 Re: [bug] Wrong bool value parameter
Previous Message PG Bug reporting form 2020-04-07 13:00:42 BUG #16347: pgbadger is missing in the repo