diff options
author | Stephan Bergmann <sbergman@redhat.com> | 2012-05-16 22:09:21 +0200 |
---|---|---|
committer | Stephan Bergmann <sbergman@redhat.com> | 2012-05-16 22:09:21 +0200 |
commit | d015384e1d98fe77fd59339044f58efb1ab9fb25 (patch) | |
tree | 27972d297a53f302b148f542d11983b54328496c /icu/icu4c-rpath.patch | |
parent | 9aad89df8757d4570084424e63b9562a13448bde (diff) |
Fixed ThreadPool (and dependent ORequestThread) life cycle
At least with sw_complex test under load, it happened that an ORequestThread
could still process a remote release request while the main thread was already
in exit(3). This was because (a) ThreadPool never joined with the spawned
worker threads (which has been rectified by calling uno_threadpool_dispose(0)
from the final uno_threadpool_destroy), and (b) binaryurp::Bridge called
uno_threadpool_destroy only from its destructor (which could go as late as
exit(3)) instead of from terminate.
Additional clean up:
* Access to Bridge's threadPool_ is now cleanly controlled by mutex_ (even
though that might not be necessary in every case).
* ThreadPool's stopDisposing got renamed to destroy, to make meaning clearer.
Change-Id: I45fa76e80e790a11065e7bf8ac9d92af2e62f262
Diffstat (limited to 'icu/icu4c-rpath.patch')
0 files changed, 0 insertions, 0 deletions