valgrind: m_mallocfree.c:268 (mk_plain_bszB): Assertion 'bszB != 0' failed | AND | valgrind: m_mallocfree.c:294 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed. | AFTER various Bitmap Valgrind errors

Bug #1184468 reported by Roel Van de Paar on 2013-05-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Confirmed
High
Laurynas Biveinis
5.1
New
Undecided
Unassigned
5.5
New
Undecided
Unassigned
5.6
Confirmed
High
Laurynas Biveinis

Bug Description

valgrind: m_mallocfree.c:294 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
valgrind: Heap block lo/hi size mismatch: lo = 98, hi = 0.
This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata. If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away. Please try that before reporting this as a bug.

And (another trial):

valgrind: m_mallocfree.c:268 (mk_plain_bszB): Assertion 'bszB != 0' failed.
valgrind: This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata. If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away. Please try that before reporting this as a bug.

And this after various other bitmap related (inc one strncpy) Valgrind messages. Full error logs attached for review.

Tags: qa Edit Tag help
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :

For reference, run commands

[roel@qaserver 271485]$ cat cmd654
ps -ef | grep 'cmdrun_654' | grep -v grep | awk '{print $2}' | xargs sudo kill -9
rm -Rf /ssd/271485/cmdrun_654
mkdir /ssd/271485/cmdrun_654
cd /ssd/randgen
bash -c "set -o pipefail; perl runall.pl --queries=100000000 --seed=578 --duration=300 --querytimeout=60 --short_column_names --reporter=Shutdown,Backtrace,QueryTimeout,ErrorLog,ErrorLogAlarm --mysqld=--log-output=none --mysqld=--sql_mode=ONLY_FULL_GROUP_BY --grammar=conf/percona_qa/5.6/5.6.yy --gendata=conf/percona_qa/5.6/5.6.zz --basedir=/ssd/Percona-Server-5.6.10-alpha60.2-347-debug-valgrind.Linux.x86_64 --valgrind --reporter=ValgrindErrors --validator=MarkErrorLog --threads=1 --views --mysqld=--slow_query_log --mysqld=--innodb_track_changed_pages=1 --mysqld=--innodb_max_bitmap_file_size=4097 --mysqld=--innodb_changed_pages=ON --mysqld=--innodb_max_changed_pages=2 --mysqld=--userstat --mysqld=--innodb_flush_method=O_DIRECT --mysqld=--innodb_file_per_table=1 --mysqld=--innodb_file_format=barracuda --mtr-build-thread=740 --mask=29089 --vardir1=/ssd/271485/cmdrun_654 > /ssd/271485/cmdrun654.log 2>&1"
[roel@qaserver 271485]$ cat cmd996
ps -ef | grep 'cmdrun_996' | grep -v grep | awk '{print $2}' | xargs sudo kill -9
rm -Rf /ssd/271485/cmdrun_996
mkdir /ssd/271485/cmdrun_996
cd /ssd/randgen
bash -c "set -o pipefail; perl runall.pl --queries=100000000 --seed=26384 --duration=300 --querytimeout=60 --short_column_names --reporter=Shutdown,Backtrace,QueryTimeout,ErrorLog,ErrorLogAlarm --mysqld=--log-output=none --mysqld=--sql_mode=ONLY_FULL_GROUP_BY --grammar=conf/percona_qa/5.6/5.6.yy --gendata=conf/percona_qa/5.6/5.6.zz --basedir=/ssd/Percona-Server-5.6.10-alpha60.2-347-debug-valgrind.Linux.x86_64 --valgrind --reporter=ValgrindErrors --validator=MarkErrorLog --threads=1 --validator=Transformer --mysqld=--slow_query_log --mysqld=--innodb_track_changed_pages=1 --mysqld=--innodb_max_bitmap_file_size=4097 --mysqld=--innodb_changed_pages=ON --mysqld=--innodb_max_changed_pages=2 --mysqld=--userstat --mysqld=--innodb_log_file_size=1048576 --mysqld=--innodb_log_files_in_group=10 --mysqld=--innodb_log_buffer_size=10485761 --mysqld=--innodb_file_per_table=1 --mysqld=--innodb_file_format=barracuda --mtr-build-thread=761 --mask=40187 --vardir1=/ssd/271485/cmdrun_996 > /ssd/271485/cmdrun996.log 2>&1"

The first Valgrind error (conditional jump is ... ) is bug 1182793.

The next ones must be either bug 1179974 exactly, either should be fixed together anyway. Closing this one as duplicate and raising bug 1179974 priority.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers