Open GoogleCodeExporter opened 9 years ago
This was a good call; I think this fix gives us the "happy medium" between not
being able to control our lifecycle and not being able to use the browser's
lifecycle. With this fix a returned shared_ptr will be managed by the browser
-- unless the browserhost or something else excplicitly releases it first,
which is still an option (an important one).
If you return a weak_ptr, the lifecycle will be managed purely by you.
Fixed in 1.4 branch, will be in RC1
Original comment by taxilian
on 10 Feb 2011 at 6:20
Original issue reported on code.google.com by
mital.d....@gmail.com
on 9 Feb 2011 at 7:05