Bug #14903 | memory block lost in the innodb handler | ||
---|---|---|---|
Submitted: | 12 Nov 2005 22:58 | Modified: | 13 Nov 2005 16:29 |
Reporter: | Oleksandr Byelkin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0.17 | OS: | Linux (linux) |
Assigned to: | CPU Architecture: | Any |
[12 Nov 2005 22:58]
Oleksandr Byelkin
[13 Nov 2005 16:29]
Heikki Tuuri
Hmm... it may be that also someone else reported a memory leak in pthread_create(). But I do not think it occurs on all platforms. When looking at srv0start.c, we see that the call os_thread_create() on that particular line 1240 passes a parameter to the function that is called first after the thread has been created. Other calls in that file pass NULL. Could it be that __pthread_initialize_manager in such case indeed leaks 8160 bytes? The parameter itself is not leaked, it is simply an integer stored in static memory. ==3025== at 0x1B901AB8: malloc (vg_replace_malloc.c:130) ==3025== by 0x1BA8AA9E: __pthread_initialize_manager (in /lib/libpthread-0.10.so) ==3025== by 0x1BA8AF1A: pthread_create@@GLIBC_2.1 (in /lib/libpthread-0.10.so) I do not think we need to care about this Valgrind warning. I am closing this bug report. Regards, Heikki