Bug #37363 | Mysql test has memory leak when query fails | ||
---|---|---|---|
Submitted: | 12 Jun 2008 12:22 | Modified: | 30 Jul 2008 16:07 |
Reporter: | Jørgen Løland | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Tests | Severity: | S3 (Non-critical) |
Version: | 6.0.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[12 Jun 2008 12:22]
Jørgen Løland
[11 Jul 2008 21:01]
Sveta Smirnova
Thank you for the report. I tested with debugger with current 6.0 bzr tree: 1. Create file bug37363.test: let $i=5; while ($i) { --error 1064 select 1+; } 2. Run ./mysql-test-run.pl bug37363 3. In other window: gdb ~/bzr/mysql-6.0/client/.libs/mysqltest PID ... (gdb) b 6578 (string where dynstr_free(&ds_warnings); is calling) (gdb) c Continuing. Breakpoint 1, run_query (cn=0xaaf10, command=0x1818418, flags=3) at mysqltest.c:6578 6578 dynstr_free(&ds_warnings); (gdb) p command->query $5 = 0x1101bd8 "select 1+" It shows ds_warnings frees even if query fails. Please correct me if my test is wrong.
[30 Jul 2008 8:38]
Jørgen Løland
I'm no longer able to reproduce the memory-not-freed warning.
[30 Jul 2008 16:07]
Sveta Smirnova
Thank you for the feedback. Set to "Can't repeat", because last comment.