You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@msekoranja states that a Requester should never hold a strong reference (shared_ptr) to the associated Operation. Doing so creates a reference loop which must be explicitly broken as the Operation holds a strong ref. to its Requester. For example, in testTop/dbPv/src/testDbPv.cpp where MyRequester does so for both Channel and ChannelGet. I don't think there is a leak as ->destroy() is called to explicitly break the loop. Still, one of the few example someone might find, and it's not best practice.
The text was updated successfully, but these errors were encountered:
From the discussion in epics-base/pvAccessCPP#60 I've looked for code using PVA.
@msekoranja states that a Requester should never hold a strong reference (shared_ptr) to the associated Operation. Doing so creates a reference loop which must be explicitly broken as the Operation holds a strong ref. to its Requester. For example, in testTop/dbPv/src/testDbPv.cpp where MyRequester does so for both Channel and ChannelGet. I don't think there is a leak as ->destroy() is called to explicitly break the loop. Still, one of the few example someone might find, and it's not best practice.
The text was updated successfully, but these errors were encountered: