Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.0.19
-
None
-
Fedora 21
Description
Executing the following query causes a memory leak of 8,224 bytes in the embedded library.
CREATE EVENT myevent ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL 1 HOUR DO UPDATE t1 SET id = id + 1;
|
The output of Valgrind at the time of the leak.
==29961== 153,504 (+25,584) (49,344 (+8,224) direct, 104,160 (+17,360) indirect) bytes in 6 (+1) blocks are definitely lost in loss record 399 of 406
|
==29961== at 0x4C29BCF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
|
==29961== by 0x72D426: my_malloc (in /home/markus/build/bin/maxscale)
|
==29961== by 0x71941F: init_alloc_root (in /home/markus/build/bin/maxscale)
|
==29961== by 0x601BC4: init_sql_alloc(st_mem_root*, unsigned int, unsigned int, unsigned long) (in /home/markus/build/bin/maxscale)
|
==29961== by 0x5B2FD5: sp_head::operator new(unsigned long) (in /home/markus/build/bin/maxscale)
|
==29961== by 0x7EFDA2: MYSQLparse(THD*) (in /home/markus/build/bin/maxscale)
|
==29961== by 0x6DC766: parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool) (in /home/markus/build/bin/maxscale)
|
==29961== by 0x1C54271A: create_parse_tree(THD*) (query_classifier.cc:380)
|
==29961== by 0x1C542186: parse_query (query_classifier.cc:199)
|
==29961== by 0x1C541ED0: query_classifier_get_type (query_classifier.cc:110)
|
==29961== by 0x1C330A61: route_single_stmt (readwritesplit.c:2081)
|
==29961== by 0x1C3303FB: routeQuery (readwritesplit.c:1976)
|
==29961==
|
==29961== LEAK SUMMARY:
|
==29961== definitely lost: 49,376 (+8,224) bytes in 7 (+1) blocks
|
==29961== indirectly lost: 104,160 (+17,360) bytes in 54 (+9) blocks
|
==29961== possibly lost: 270,928,208 (-60,840) bytes in 215 (-21) blocks
|
==29961== still reachable: 1,280,312 (+0) bytes in 1,004 (+0) blocks
|
==29961== suppressed: 0 (+0) bytes in 0 (+0) blocks
|
==29961== Reachable blocks (those to which a pointer was found) are not shown.
|
==29961== To see them, add 'reachable any' args to leak_check
|
 |
MaxScale uses the embedded library only to parse queries and it seems to leak the memory when the free_embedded_thd function for the THD is called when MaxScale is done with it.
Attachments
Issue Links
- blocks
-
-
- Closed
-