[MDEV-20956] binlog_encryption.rpl_mixed_binlog_max_cache_size failed in buildbot: incorrect checksum for freed object Created: 2019-11-03  Updated: 2019-11-03

Status: Open
Project: MariaDB Server
Component/s: Encryption, Replication
Affects Version/s: 10.4
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/mac-1012-bintar/builds/5972

10.4 e2f570bff872532dcae5f2cf882e01f4

binlog_encryption.rpl_mixed_binlog_max_cache_size 'mix' [ fail ]
        Test ended at 2019-09-10 09:37:38
 
CURRENT_TEST: binlog_encryption.rpl_mixed_binlog_max_cache_size
mysqltest: In included file "./include/rpl_connect.inc": 
included from ./include/master-slave.inc at line 46:
included from /Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/suite/binlog_encryption/rpl_mixed_binlog_max_cache_size.test at line 2:
At line 55: query 'connect  $rpl_connection_name,127.0.0.1,root,,test,$_rpl_port,' failed: 2013: Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 60
 
The result from queries just before the failure was:
include/master-slave.inc

2019-09-10  9:35:38 13 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000001, 4)
mysqld(87086,0x70000679b000) malloc: *** error for object 0x7fddf6d31c00: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
190910  9:35:38 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
 
Server version: 10.4.8-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=6
max_threads=153
thread_count=13
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63511 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fddf7139a08
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x49000


Generated at Thu Feb 08 09:03:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.