Bug #24475 Instance Manager: a memory leak
| Submitted: | 21 Nov 2006 14:54 | Modified: | 5 Oct 2007 15:20 |
|---|---|---|---|
| Reporter: | Alexander Nozdrin | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | Instance Manager | Severity: | S3 (Non-critical) |
| Version: | 5.1 BK | OS: | Linux (Linux) |
| Assigned to: | CPU Architecture: | Any |
[22 Nov 2006 10:18]
Sveta Smirnova
Thank you for the report. Verified as described on Linux using last BK sources.
[5 Oct 2007 15:20]
Konstantin Osipov
Setting to Unsupported unless the decision to discontinue is reverted.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: If Instance Manager has been started with --debug option, on shutdown it warns about memory leak. How to repeat: (booka)[~/MySQL/devel/5.1-rt-im/server-tools/instance-manager]> ./mysqlmanager --debug 06/11/21 17:52:50 Loading config file '/etc/my.cnf'... 06/11/21 17:52:50 Detected threads model: POSIX threads. 06/11/21 17:52:50 password file (/etc/mysqlmanager.passwd) does not exist. Warning: Not freed memory segments: 1 Warning: Memory that was not free'ed (456 bytes): 456 bytes at 0x0081ad598, allocated at line 197 in 'my_alloc.c' Maximum memory usage: 712 bytes (1k)