-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A few memory leaks #48
Comments
which branch does do these refer to? |
The master branch. Just realized that exists the policy-refactor branch and is far as I understood, it is a trunk branch now. Correct? |
That is right. The policy refactor branch was unstable and feature incomplete for awhile so I worked on it separately from the old (but working) master branch. policy-refactor is largely done now and is just going through some final testing now before I merge it all back into master. Regarding these errors in policy-refactor, the cyclic dependency between the endpoint/connection (previously server/session) was already resolved. I am working now on wrapping the io_service run, stop, reset calls to ensure that existing connections are cleaned up properly. |
I see.. I think it possible to close the issue. I downloaded the policy-refactor branch. Compiled the library under Windows. It was required to add new files and remove legacy ones. Surely the chat sample is not compilable, but the fuzzing_client is not compilable also. Is the fuzzing_client example possible to compile under Linux? |
I only have only started bringing the older examples up to spec with policy-refactor in the last week or so. The following should definitely be current:
fuzzing client/server and chat client/server may not be running yet on the latest build. I'll check, if not they should be trivial to fix. |
Thank you a lot. I will try to compile the these examples under Windows. |
There are the following memory leaks:
To resolve this cyclic dependency is necessary to use the boost::weak_ptr class instead of boost::shared_ptr for the client_session::m_client member.
The text was updated successfully, but these errors were encountered: