general/6824: mutex does not be destroyed on UNIX (APR_USE_PTHREAD_SERIALIZE)

[Shuichi Kitaguchi <ki...@hh.iij4u.or.jp>]

>Number:         6824
>Category:       general
>Synopsis:       mutex does not be destroyed on UNIX (APR_USE_PTHREAD_SERIALIZE)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Nov 09 06:40:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     ki@hh.iij4u.or.jp
>Release:        2.0a7
>Organization:
apache
>Environment:
FreeBSD 4.1.1-STABLE
gcc-2.95.2
>Description:
lock functions in APR seem to do not call pthread_mutex_destroy when APR_USE_PTHREAD_SERIALIZED is defined.  Thus, Apache leaks a bit of memory whenever use lock functions.  I think pthread_mutex_destroy must be called in lock_intra_cleanup@apr/locks/unix/intraproc.c and lock_cleanup@apr/locks/unix/crossproc.c (or more).
>How-To-Repeat:

>Fix:
add pthread_mutex_destroy() to lock functions.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]