Valgrind errors at InnoDB initialization

Bug #791849 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
percona-projects-qa
Fix Released
Medium
Laurynas Biveinis

Bug Description

Observed in many tests, for example, with main.create:

128 bytes in 1 blocks are possibly lost in loss record 96 of 134
   at 0x4C2815C: malloc (vg_replace_malloc.c:236)
   by 0xB31A6B: mem_area_alloc (mem0pool.c:385)
   by 0xB2FDBB: mem_heap_create_block (mem0mem.c:333)
   by 0xA7403C: mem_heap_create_func (mem0mem.ic:443)
   by 0xA74239: mem_alloc_func (mem0mem.ic:529)
   by 0xA78814: btr_search_sys_create (btr0sea.c:195)
   by 0xA8585A: buf_pool_init (buf0buf.c:1902)
   by 0xA148CE: innobase_start_or_create_for_mysql (srv0start.c:1511)
   by 0x9B149F: innobase_init(void*) (ha_innodb.cc:2858)
   by 0x755442: ha_initialize_handlerton(st_plugin_int*) (handler.cc:462)
   by 0x5E7493: plugin_initialize(st_plugin_int*) (sql_plugin.cc:1063)
   by 0x5E7EC6: plugin_init(int*, char**, int) (sql_plugin.cc:1349)
   by 0x52DB40: init_server_components() (mysqld.cc:3960)
   by 0x52EC72: mysqld_main(int, char**) (mysqld.cc:4634)
   by 0x526E53: main (main.cc:24)

128 bytes in 1 blocks are definitely lost in loss record 97 of 134
   at 0x4C2815C: malloc (vg_replace_malloc.c:236)
   by 0xB31A6B: mem_area_alloc (mem0pool.c:385)
   by 0xB2FDBB: mem_heap_create_block (mem0mem.c:333)
   by 0xA7403C: mem_heap_create_func (mem0mem.ic:443)
   by 0xA74239: mem_alloc_func (mem0mem.ic:529)
   by 0xA78846: btr_search_sys_create (btr0sea.c:196)
   by 0xA8585A: buf_pool_init (buf0buf.c:1902)
   by 0xA148CE: innobase_start_or_create_for_mysql (srv0start.c:1511)
   by 0x9B149F: innobase_init(void*) (ha_innodb.cc:2858)
   by 0x755442: ha_initialize_handlerton(st_plugin_int*) (handler.cc:462)
   by 0x5E7493: plugin_initialize(st_plugin_int*) (sql_plugin.cc:1063)
   by 0x5E7EC6: plugin_init(int*, char**, int) (sql_plugin.cc:1349)
   by 0x52DB40: init_server_components() (mysqld.cc:3960)
   by 0x52EC72: mysqld_main(int, char**) (mysqld.cc:4634)
   by 0x526E53: main (main.cc:24)

Server built with -DWITH_DEBUG=ON -DWITH_VALGRIND=ON

Related branches

Changed in percona-projects-qa:
milestone: none → 5.5.12-20.3
Revision history for this message
Oleg Tsarev (tsarev) wrote :
Download full text (3.7 KiB)

Bug was reproduced on Fedora x86_64 release vesrsion
oleg.tsarev (0) /storage/dev/percona/5.5.12/Percona-Server-release/mysql-test$ ./mysql-test-run main.percona_xtradb_bug317074 --valgrind
Logging: /storage/dev/percona/5.5.12/Percona-Server/mysql-test/mysql-test-run.pl main.percona_xtradb_bug317074 --valgrind
110602 18:25:11 [Note] Flashcache bypass: disabled
110602 18:25:11 [Note] Flashcache setup error is : open flash device failed

MySQL Version 5.5.12
Turning on valgrind for all executables
Running valgrind with options " --show-reachable=yes "
Checking supported features...
 - skipping ndbcluster
 - skipping SSL, mysqld not compiled with SSL
Collecting tests...
vardir: /storage/dev/percona/5.5.12/Percona-Server-release/mysql-test/var
Removing old var directory...
Creating var directory '/storage/dev/percona/5.5.12/Percona-Server-release/mysql-test/var'...
Installing system database...
Using server port 48481

==============================================================================

TEST RESULT TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
main.percona_xtradb_bug317074 [ pass ] 255714
worker[1] Valgrind report from /storage/dev/percona/5.5.12/Percona-Server-release/mysql-test/var/log/mysqld.1.err after tests:
 main.percona_xtradb_bug317074
--------------------------------------------------------------------------
HEAP SUMMARY:
    in use at exit: 30,570,344 bytes in 207 blocks
  total heap usage: 1,464,025 allocs, 1,463,818 frees, 7,849,406,315 bytes allocated

128 bytes in 1 blocks are possibly lost in loss record 107 of 136
   at 0x4A05E46: malloc (vg_replace_malloc.c:195)
   by 0x932408: mem_area_alloc (mem0pool.c:385)
   by 0x93168E: mem_heap_create_block (mem0mem.c:333)
   by 0x89F23E: btr_search_sys_create (mem0mem.ic:443)
   by 0x8A9B23: buf_pool_init (buf0buf.c:1902)
   by 0x85D4DA: innobase_start_or_create_for_mysql (srv0start.c:1511)
   by 0x82068C: innobase_init(void*) (ha_innodb.cc:2858)
   by 0x688197: ha_initialize_handlerton(st_plugin_int*) (handler.cc:462)
   by 0x58A889: plugin_initialize(st_plugin_int*) (sql_plugin.cc:1063)
   by 0x58FA87: plugin_init(int*, char**, int) (sql_plugin.cc:1349)
   by 0x50EE25: init_server_components() (mysqld.cc:3962)
   by 0x51259C: mysqld_main(int, char**) (mysqld.cc:4634)
   by 0x37E701EE5C: (below main) (libc-start.c:226)

128 bytes in 1 blocks are definitely lost in loss record 109 of 136
   at 0x4A05E46: malloc (vg_replace_malloc.c:195)
   by 0x932408: mem_area_alloc (mem0pool.c:385)
   by 0x93168E: mem_heap_create_block (mem0mem.c:333)
   by 0x89F2CF: btr_search_sys_create (mem0mem.ic:443)
   by 0x8A9B23: buf_pool_init (buf0buf.c:1902)
   by 0x85D4DA: innobase_start_or_create_for_mysql (srv0start.c:1511)
   by 0x82068C: innobase_init(void*) (ha_innodb.cc:2858)
   by 0x688197: ha_initialize_handlerton(st_plugin_int*) (handler.cc:462)
   by 0x58A889: plugin_initialize(st_plugin_int*) (sql_plugin.cc:1063)
   by 0x58FA87: plugin_init(int*, char**, int) (sql_plugin.cc:1349)
   by 0x50EE25: init_server_components() (mysqld.cc:3962)
   by 0x51259C: mysqld_main(int,...

Read more...

Changed in percona-projects-qa:
status: New → Confirmed
Oleg Tsarev (tsarev)
Changed in percona-projects-qa:
assignee: nobody → Stewart Smith (stewart)
Stewart Smith (stewart)
Changed in percona-projects-qa:
assignee: Stewart Smith (stewart) → nobody
Changed in percona-projects-qa:
assignee: nobody → Laurynas Biveinis (laurynas-biveinis)
importance: Undecided → Medium
Changed in percona-projects-qa:
status: Confirmed → In Progress
Changed in percona-projects-qa:
status: In Progress → Fix Committed
Changed in percona-projects-qa:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.