| Bug #28644 | Memory status report confused with memory leak | ||
|---|---|---|---|
| Submitted: | 24 May 2007 10:11 | Modified: | 29 Jun 2007 0:05 |
| Reporter: | Kristofer Pettersson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Kristofer Pettersson | CPU Architecture: | Any |
[24 May 2007 11:12]
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: http://lists.mysql.com/commits/27268 ChangeSet@1.2656, 2007-05-24 13:11:45+02:00, thek@adventure.(none) +2 -0 Bug#28644 Memory status report confused with memory leak This patch removes a false memory leak error report from the test suite. There is a test case that puposely provokes a SAFEMALLOC leak report, even though there is no actual leak.
[24 May 2007 11:22]
Daniel Fischer
Looks okay. PB part is also done (hopefully).
[1 Jun 2007 19:23]
Bugs System
Pushed into 5.1.20-beta
[29 Jun 2007 0:05]
Konstantin Osipov
Internal bug, was fixed together with the build team.
Description: Pushbuild reports memory status report from a COM_DEBUG as a memory leak error. Example: WARNING: 'Not freed memory segments: 500' COUNT: 1 FILES: master.err TESTS: mysql_client_test WARNING: 'Memory that was not free'ed (2213940 bytes):' COUNT: 1 FILES: master.err TESTS: mysql_client_test Only after when this status report is called from my_end should this report have any significance. How to repeat: mysql-test/mtr mysql_client_test Suggested fix: Wrap status data with a header and footer: Begin safemalloc memory dump: . . End safemalloc memory dump. Add filter to pushbuild and mysql-test-run to ignore this tag.