Bug 134376

The manpages for pthread(3), pthread_mutex_lock(5), pthread_mutex_init(3), pthread_mutex_destroy(3) make no mention of PTHREAD_MUT
EX_INITIALIZER, and that using it in a loop causes memory leaks.                                                                          
It  is obvious that PTHREAD_MUTEX_INITIALIZER acts like pthread_mutex_init, which on FreeBSD allocates memory.                    
If pthread_mutex_destroy is not called this results in a 60 byte memory leak (on amd64), which in turn can cause long running daemons to r
un out of memory as described here: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1567#c33, and here: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1567#c32                                                                                 
 
        Although portable programs shouldn't rely on knowing the implementation details of pthreads, knowing that it allocates memory can
(and maybe other implementation details) can provide useful debugging hints when something goes wrong.

Fix: 

PTHREAD_MUTEX_INITIALIZER doesn't appear in any of the pthread manpages, it should be added.                                 
        The FreeBSD manpages for pthread_mutex_lock, or pthread_mutex_init should document that on FreeBSD memory is allocated when these 
functions are used (I was not aware of this for example), and that one shouldn't use PTHREAD_MUTEX_INITIALIZER in code that is possibly ca
lled in a loop. Since you can't pthread_mutex_destroy a mutex "allocated" with PTHREAD_MUTEX_INITIALIZER, the manpage should recommend the
use of pthread_mutex_init/pthread_mutex_destroy in this case.
        By reading the /usr/include/pthread.h file I realize that PTHREAD_MUTEX_INITIALIZER is actually NULL, so I guess memory allocation
 happens on first pthread_mutex_lock call, maybe the manpage should document that.
How-To-Repeat: Assign PTHREAD_MUTEX_INITIALIZER to a variable in a function, call pthread_mutex_lock/unlock, call function in a loop ->          
there is a 60-byte memory leak. Look at pthread manpages for clues about what can be wrong, find no clues.