Memory access error on corrupted mysql.slave_relay_log_info

Description

Testcase

/qa/ps8/PS291118-percona-server-8.0.12-2-linux-x86_64-debug/bin/mysqld --no-defaults --initialize-insecure --basedir=/qa/ps8/PS291118-percona-server-8.0.12-2-linux-x86_64-debug --datadir=/dev/shm/1544200424/data valgrind --suppressions=/qa/ps8/PS291118-percona-server-8.0.12-2-linux-x86_64-debug/mysql-test/valgrind.supp --num-callers=40 --show-reachable=yes /qa/ps8/PS291118-percona-server-8.0.12-2-linux-x86_64-debug/bin/mysqld --no-defaults --basedir=/qa/ps8/PS291118-percona-server-8.0.12-2-linux-x86_64-debug --datadir=/dev/shm/1544200424/data --port=32094 --tmpdir=/dev/shm/1544200424/tmp --pid-file=/dev/shm/1544200424/pid.pid --core-file --log-error=/dev/shm/1544200424/error.log.out --socket=/dev/shm/1544200424/socket.sock & SQL start slave until master_log_file='master-bin.0',master_log_pos=0; SET @@global.table_open_cache=-0; ALTER TABLE mysql.slave_relay_log_info DROP COLUMN Number_of_workers; Shutdown the server and analyze the error log.

Environment

None

Attachments

1
  • 08 Dec 2018, 07:40 AM

Smart Checklist

Activity

Show:

Julia Vural March 4, 2025 at 9:02 PM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

Ramesh Sivaraman December 10, 2018 at 10:38 AM

ack

Laurynas Biveinis December 10, 2018 at 10:07 AM

, "Invalid read of size 8" is not a memory leak, and this error might be reproduced with an ASan build too.

(please also make sure that any server for Valgrind testing is always built with -DWITH_VALGRIND=ON)

Ramesh Sivaraman December 10, 2018 at 8:53 AM

Reproduced with upstream 8.0.13 build : https://bugs.mysql.com/bug.php?id=93538

Laurynas Biveinis December 10, 2018 at 7:38 AM

Upstream status?

Won't Do

Details

Assignee

Reporter

Affects versions

Priority

Smart Checklist

Created December 8, 2018 at 7:40 AM
Updated March 4, 2025 at 9:02 PM
Resolved March 4, 2025 at 9:02 PM