[MDEV-30697] Memory leak detected when mariadb-binlog is used with option flashback Created: 2023-02-21  Updated: 2023-03-08  Resolved: 2023-03-08

Status: Closed
Project: MariaDB Server
Component/s: Replication, Scripts & Clients
Affects Version/s: 10.11
Fix Version/s: 10.4.29

Type: Bug Priority: Major
Reporter: Anel Husakovic Assignee: Andrew Hutchings
Resolution: Fixed Votes: 0
Labels: Papercut

Issue Links:
Relates
relates to MDBF-533 Coverity scan: Add model file to repo... Open

 Description   

When mariadb-binlog is used with flasback option without server running, we can detect memory leak.

$ ./client/mysqlbinlog mysql-test/var/tmp/mysqlbinlog_row_flashback_3.sql  --flashback
 
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!40019 SET @@session.max_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
ERROR: File is not a binary log file.
Warning: 8216 bytes lost at 0x5604067a20a0, allocated by T@0 at mysys/array.c:73, client/mysqlbinlog.cc:3589, addr2line: DWARF error: section .debug_info is larger than its filesize! (0x93ef57 vs 0x530ea0)
??:0, ??:0
Warning: 16408 bytes lost at 0x56040679e000, allocated by T@0 at mysys/array.c:73, client/mysqlbinlog.cc:3587, addr2line: DWARF error: section .debug_info is larger than its filesize! (0x93ef57 vs 0x530ea0)
??:0, ??:0
Memory lost: 24624 bytes in 2 chunks

This bug is not catched by Coverity scan.


Generated at Thu Feb 08 10:18:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.