apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48722] apr_thread_pool_push may not create a new thread when necessary
Date Thu, 16 Jun 2011 22:41:37 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48722

--- Comment #5 from Alex Korobka <akorobka@fxcm.com> 2011-06-16 22:41:37 UTC ---
Original example has a race condition between DO_PUSH() using mp pool to
allocate synchronization objects in the main thread and thread pool worker
function using the same mp pool to allocate internal objects. Version in the
previous attachment fixes that.

Also, the deadlock can be avoided by bumping up the number of the initial
threads. However this exposes another problem. If apr_thread_pool_destroy() is
called quickly after creating a thread pool with a large number of initial
threads it seems to leave some of them still executing inside
thread_pool_func(), which causes another crash.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org


Mime
View raw message