Bug #102327 Possible memory leaks in mysqld

• Submitted: 21 Jan 2021 7:45
• Modified: 21 Jan 2021 9:29
• Reporter: Venkatesh Prasad Venugopal
• Status: Verified
• Category: MySQL Server: Options
• Severity: S3 (Non-critical)
• Version: 8.0.23
• OS: Any
• CPU Architecture: Any

[21 Jan 2021 7:45] Venkatesh Prasad Venugopal

Description:
Valgrind reports possible memory leaks when we run mysqld with basic options like --help or  --validate-config.

$ ./bin/mysqld --version                                                                 
/work/mysql/80/bld/runtime_output_directory/mysqld  Ver 8.0.23-debug for Linux on x86_64 (Source distribution)

$ valgrind --leak-check=full --show-leak-kinds=all ../bin/mysqld --validate-config
..
==92714== 
==92714== LEAK SUMMARY:
==92714==    definitely lost: 0 bytes in 0 blocks
==92714==    indirectly lost: 0 bytes in 0 blocks
==92714==      possibly lost: 3,437 bytes in 51 blocks
==92714==    still reachable: 4,520 bytes in 50 blocks
==92714==         suppressed: 0 bytes in 0 blocks
==92714== 
==92714== For lists of detected and suppressed errors, rerun with: -s
==92714== ERROR SUMMARY: 7 errors from 7 contexts (suppressed: 0 from 0)

How to repeat:
Run valgrind --leak-check=full --show-leak-kinds=all ../bin/mysqld --validate-config

[21 Jan 2021 7:46] Venkatesh Prasad Venugopal

valgrind output

Attachment: mysqld_valgrind.txt (text/plain), 254.28 KiB.

[21 Jan 2021 9:29] MySQL Verification Team

Hello Venu,

Thank you for the report and feedback.

regards,
Umesh