Skip to content
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

lifetime of components doesn't end when client goes out of scope #254

brycelelbach opened this issue Jul 10, 2012 · 1 comment


None yet
1 participant
Copy link

commented Jul 10, 2012

[reported by heller] [Trac time Sat Nov 5 15:01:52 2011] The test at:
shows that once the client representation of a component goes out of scope, the server side representation isn't properly destructed.
The output of the program is the following:
start of hpx_main
end of hpx_main


This comment has been minimized.

Copy link
Member Author

commented Jul 10, 2012

[comment by heller] [Trac time Sat Nov 5 21:29:49 2011] Seems like i misinterpreted the output.
According to Hartmut and Bryce, the effec that can be seen here is due to the indeterministic behavior of the actual garbage collection (the id_types are reference counted, but the the thread to delete the components might be delayed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.