MySQL Bugs: #41187: falcon.falcon_bug_23818_I failed with valgrind warning

Bug #41187	falcon.falcon_bug_23818_I failed with valgrind warning
Submitted:	2 Dec 2008 20:06	Modified:	10 Dec 2008 15:28
Reporter:	Sven Sandberg	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Tests: Engine	Severity:	S7 (Test Cases)
Version:	6.0	OS:	Any
Assigned to:	Vladislav Vaintroub	CPU Architecture:	Any
Tags:	F_TEST, falcon_bug_23818_I, pushbuild, sporadic, test failure, valgrind

Description:
pushbuild failure:

falcon.falcon_bug_23818_I                [ fail ]  Found warnings in server log file!
@log_error
/dev/shm/var-falcon-121/2/mysqld.1/mysqld.err
log_error
==21166==    at 0x4B30B58: (within /lib64/libpthread-2.4.so)
==21166==    at 0x4A20A56: malloc (vg_replace_malloc.c:149)
^ Found warnings!!

 - saving '/dev/shm/var-falcon-121/2/log/falcon.falcon_bug_23818_I/' to '/dev/shm/var-falcon-121/log/falcon.falcon_bug_23818_I/'

Retrying test, attempt(2/3)...

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=78 pb-valgrind/falcon
xref: http://tinyurl.com/6r8weg

Vlad,  This looks like a memory leak in something other than Falcon code.  Can you confirm?

Sven, the last valgrind runs look have warnings for mysqltest, not mysqld.
Sounds like a problem with new MTR. Could you please check and assign to appropriate person?
Thanks

This is a problem with mysqld, not mysqltest. (There are problems with mysqltest but they are not related to this bug.)

This failure has only happened once and there is not enough debug info that it can be analyzed. Setting to "Can't repeat". Please reopen the bug if it happens again.