Valgrind: memory leak in scalability_metrics
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
5.6 |
Fix Released
|
Medium
|
Sergei Glushchenko |
Bug Description
./mysql-test-run scalability_metrics
main.scalabilit
worker[1] Valgrind report from /home/laurynas/
main.scalabili
-------
HEAP SUMMARY:
in use at exit: 30,570,392 bytes in 215 blocks
total heap usage: 61,713 allocs, 61,498 frees, 90,904,355 bytes allocated
32 bytes in 1 blocks are definitely lost in loss record 30 of 100
at 0x4C2CC70: calloc (in /usr/lib/
by 0x1202F43A: ???
by 0x1202F877: ???
by 0x1202FC88: ???
by 0x6ED1E3: plugins_
by 0x6ED28A: event_class_
by 0x6EC352: general_
by 0x6ECC92: mysql_audit_
by 0x5F65CF: mysql_audit_
by 0x5F9DD6: dispatch_
by 0x5F7CC0: do_command(THD*) (sql_parse.cc:789)
by 0x6F0C0D: do_handle_
by 0x6F073C: handle_
by 0x9BBB8F: pfs_spawn_thread (pfs.cc:1015)
by 0x525A181: start_thread (pthread_
by 0x5FB230C: clone (clone.S:111)
64 bytes in 2 blocks are definitely lost in loss record 61 of 100
at 0x4C2CC70: calloc (in /usr/lib/
by 0x1202F43A: ???
by 0x1202FCEF: ???
by 0x6ED1E3: plugins_
by 0x6ED28A: event_class_
by 0x6EC9A4: connection_
by 0x6ECC92: mysql_audit_
by 0x6F09DF: thd_prepare_
by 0x6F0BE4: do_handle_
by 0x6F073C: handle_
by 0x9BBB8F: pfs_spawn_thread (pfs.cc:1015)
by 0x525A181: start_thread (pthread_
by 0x5FB230C: clone (clone.S:111)
plugins_dispatch is the last function in the server code, ??? and ??? are likely to be in plugin. There is a single calloc site in the plugin source, sm_thd_data_get.
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 21 lines (+2/-2)1 file modifiedplugin/scalability_metrics/scalability_metrics.c (+2/-2)
- Registry Administrators: Pending requested
- Alexey Kopytov (community): Approve
tags: | added: ci valgrind |
I can not reproduce this with 5.6.19- 66.1-debug- log