Skip Menu |
 

Subject: thread_termination doesn't free array of thread specific data
thread_termination doesn't free the array "t", causing a 4 byte leak on every thread termination
in the calling application. This causes a problem for long-running servers with lots of threads.
[lxs - Sun Mar 20 10:08:31 2005]:

Show quoted text
> thread_termination doesn't free the array "t", causing a 4 byte leak
> on every thread termination
> in the calling application. This causes a problem for long-running
> servers with lots of threads.

Sorry, that's a 16 byte leak... (4 4-byte pointers).
From: lxs@mit.edu
Subject: CVS Commit
threads.c (thread_termination): Free array of pointers to thread-specific data (t) on thread termination. Use existing mutex to prevent the deletion of the array from interfering with the global list of thread specific data (used for library termination).


To generate a diff of this commit:



cvs diff -r1.30 -r1.31 krb5/src/util/support/ChangeLog
From: lxs@mit.edu
Subject: CVS Commit
threads.c (thread_termination): Free array of pointers to thread-specific data (t) on thread termination. Use existing mutex to prevent the deletion of the array from interfering with the global list of thread specific data (used for library termination).


To generate a diff of this commit:



cvs diff -r1.18 -r1.19 krb5/src/util/support/threads.c
From: lxs@mit.edu
Subject: CVS Commit
pullup from trunk


To generate a diff of this commit:



cvs diff -r1.19.2.1 -r1.19.2.2 krb5/src/util/support/ChangeLog
From: lxs@mit.edu
Subject: CVS Commit
pullup from trunk


To generate a diff of this commit:



cvs diff -r1.11 -r1.11.4.1 krb5/src/util/support/threads.c