Bug #44710 assertion failure in mdl when server starts, related to performance schema
Submitted: 7 May 2009 9:07 Modified: 14 Jan 2010 18:04
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Performance Schema Severity:S3 (Non-critical)
Version:6.0-perfschema OS:Linux
Assigned to: Marc ALFF CPU Architecture:Any

[7 May 2009 9:07] Guilhem Bichot
I have
 3135 Marc Alff	2009-05-07
      Implemented code review comments, continued
 ./mtr --mem --start alias &
leads to
mysqld: pfs.cc:1140: PSI_mutex_locker* get_thread_mutex_locker_v1(PSI_mutex*, PSI_mutex_operation): Assertion `pfs_mutex->m_info != __null' failed.
/lib/libc.so.6(__assert_fail+0xe9) [0x7f5d21088d89]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld [0xeb9900]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld [0xe0132a]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld(safe_mutex_init+0x228) [0xe012a0]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld [0x9c8740]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld(mdl_init()+0x60) [0x9c87fe]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld [0x78334d]
/home/mysql_src/bzrrepos/mysql-6.0-perfschema/sql/mysqld(main+0x2fc) [0x78451b]

How to repeat:
see description
[7 May 2009 15:47] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


3136 Marc Alff	2009-05-07
      Bug#44710 assertion failure in mdl when server starts, related to performance schema
      The assert was related to a build warning.
      THR_LOCK_mutex is pthread_mutex_t, not a mysql_mutex_t.
      Using thread_safe_increment caused the code to use a non existent m_psi pointer.
      Fixed another build warning (bytes may not be initialized).
[1 Jun 2009 16:54] Marc ALFF
Queued in mysql-6.0-perfschema
[14 Jan 2010 10:02] Marc ALFF
Merged in:
- mysql-next-mr (Celosia / 5.5.99-m3)
- mysql-6.0-codebase (6.0.14)
[14 Jan 2010 18:04] Paul DuBois
Not in any released version. No changelog entry needed.