Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Connection is never destructed #310

Closed
otaras opened this issue Nov 26, 2013 · 4 comments
Closed

Connection is never destructed #310

otaras opened this issue Nov 26, 2013 · 4 comments

Comments

@otaras
Copy link

otaras commented Nov 26, 2013

Connection object is never destructed because its members like m_async_read_handler m_async_write_handler and m_init_handler keep shared pointer to itself (asio/connection.hpp).

@lcis
Copy link

lcis commented Dec 5, 2013

Hi,
Using the latest version I got an error message "call to empty boost::function".
Removing the changes:

  m_async_read_handler = 0;
  m_async_write_handler = 0;
  m_init_handler = 0;

works for me again.

@zaphoyd
Copy link
Owner

zaphoyd commented Dec 10, 2013

The fix for the memory leak introduced another issue. Working on a fix for this one.

@zaphoyd
Copy link
Owner

zaphoyd commented Dec 11, 2013

I've corrected some cases of the "call to empty lib::function" error. Anyone who was experiencing that issue should grab the latest master/HEAD and retest.

@lcis
Copy link

lcis commented Dec 11, 2013

Thanks!
I've tested it (server app running on a Raspberry Pi and OS X Xcode dev), so far no errors.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants