summaryrefslogtreecommitdiffstats
path: root/server
diff options
context:
space:
mode:
authorBrian Pane <brianp@apache.org>2005-12-31 08:16:09 +0100
committerBrian Pane <brianp@apache.org>2005-12-31 08:16:09 +0100
commitc821da5c78d082ffe4a55e27eb1112b580e07921 (patch)
tree91a38287f1e36dfb78c2323cc0ebdf28e1772664 /server
parentGeneral cleanup: (diff)
downloadapache2-c821da5c78d082ffe4a55e27eb1112b580e07921.tar.xz
apache2-c821da5c78d082ffe4a55e27eb1112b580e07921.zip
Removed the destruction of the bucket allocator prior to
clearing the transaction pool. The bucket allocator will now get destroyed when apr_pool_clear() invokes its cleanup callback. With the old logic, memory corruption was possible if the pool contained any brigades that referenced any buckets allocated from the bucket allocator. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@360257 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'server')
-rw-r--r--server/mpm/experimental/event/event.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/server/mpm/experimental/event/event.c b/server/mpm/experimental/event/event.c
index 622a246464..38f187d1f8 100644
--- a/server/mpm/experimental/event/event.c
+++ b/server/mpm/experimental/event/event.c
@@ -678,7 +678,6 @@ read_request:
if (cs->state == CONN_STATE_LINGER) {
ap_lingering_close(c);
- apr_bucket_alloc_destroy(cs->bucket_alloc);
apr_pool_clear(p);
ap_push_pool(worker_queue_info, p);
return 1;