[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[Libevent-users] Memory won't be freed in SSL connection.
- To: libevent-users@xxxxxxxx
- Subject: [Libevent-users] Memory won't be freed in SSL connection.
- From: 林宇舜 Yu-Shun Lin <ys.ncku@xxxxxxxxx>
- Date: Tue, 22 Feb 2011 11:52:11 +0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Mon, 21 Feb 2011 22:52:17 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=sGeKNA8A1SFzPlpHjEs1NIZlFUmmwq1rjjhdxyBEE3M=; b=Tqafz8am1aiwKIKXPgUv6x+bI/Gt7o7UfmwD16lVTltT3VyopLLKsjZBSH7CTDeV2k vny5Xbyeoa+NSxbW96W+CtSjoHo6gr/xQX6VxiJfkp6zdHpmnLKqlnBrJO+cubU+Sr6H +IJ1+8SpkmfIxru4Z6AG9kb6IpkMbgq1cl2RE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GwZSfVleXTd+l4nKYLQhAN1MSmxaJhwblntEQrY2ZbRUmApaYNwIiSx9V7tY+wDRot TN909W7mIJHC5eI5ulf49tJzXU5zGe+0pWleooKA8sQh0qXFTZOJosoxOJ/KHKJULyD6 iIa6JB9EMbHkdq/eRLUz+oI/pVelsrKL8bM9I=
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
Hi all,
I construct SSL connection by using
bev1 = bufferevent_socket_new(... fd ..., BEV_OPT_CLOSE_ON_FREE)
bev2 = bufferevent_openssl_filter_new(... bev ..., BEV_OPT_CLOSE_ON_FREE)
bufferevent_setcb(bev2, read_cb, ..., event_cb...)
And close connection by bufferevent_free(bev) in event callback.
But the memory seems only increased, don't be released.
These memory is reachable, because I terminate the program gracefully by using event_base_loopexit() and event_base_free(), the memory can be released.
Does bufferevent over SSL has any catch mechanism?
How to release them or limit the maximun size?
Or I miss some destruct functions?
Brian