[MDEV-20147] rpl.rpl_ipv4_as_ipv6 failed in buildbot with incorrect checksum for freed object Created: 2019-07-24  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Server, Tests
Affects Version/s: 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Oleksandr Byelkin
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

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

10.3 0789a1a18f0e780c0412667e7b6e0a99

rpl.rpl_ipv4_as_ipv6                     [ fail ]
        Test ended at 2019-06-15 02:21:41
 
CURRENT_TEST: rpl.rpl_ipv4_as_ipv6
mysqltest: In included file "./include/rpl_ipv6.inc": 
included from /Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/suite/rpl/t/rpl_ipv4_as_ipv6.test at line 11:
At line 1: query 'connect  master,$IPv6,root,,test,$MASTER_MYPORT' 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:
#################### IP: 127.0.0.1 ###########################
 
 - skipping '/Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/log/rpl.rpl_ipv4_as_ipv6/'

Version: '10.3.16-MariaDB-log'  socket: '/Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/tmp/mysqld.1.sock'  port: 16000  MariaDB Server
mysqld(511,0x70000c770000) malloc: *** error for object 0x7fd36ee68710: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
190615  2:19:41 [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.3.16-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=2
max_threads=153
thread_count=9
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63196 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fd3709a5608
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 = 0x70000c76fe60 thread_stack 0x49000



 Comments   
Comment by Andrei Elkin [ 2019-09-10 ]

rpl_rotate_logs.test run on Mac witnessed a similar error
http://buildbot.askmonty.org/buildbot/builders/mac-1012-bintar/builds/5960/steps/test/logs/mysqld.1.err.

2019-09-08 11:12:58 140736028590976 [Note] /Users/buildbot/maria-slave/mac-1012-
Version: '10.2.27-MariaDB-log'  socket: '/Users/buildbot/maria-slave/mac-1012-bi
mysqld(53133,0x700004ba2000) malloc: *** error for object 0x7fc76f602ca0: incorr
*** set a breakpoint in malloc_error_break to debug
190908 11:12:58 [ERROR] mysqld got signal 6 ;

Generated at Thu Feb 08 08:57:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.