Re: atscppapi: AsyncHttpFetch question

Can you try putting a message in the destructor (as Alan suggested) or running it under gdb and setting a breakpoint? Please file an issue if it is still a problem: https://github.com/apache/trafficserver/issues -Bryan > On Mar 22, 2017, at 5:0

Re: atscppapi: AsyncHttpFetch question

Yes, it looks like it should clean up after itself but apparently isn't. I'd try putting a debug message in the destructor and verify it at least is getting called. I haven't looked at that code myself unfortunately. > Hi, > The motivation for my question is because I am seeing a small leak in m

Re: atscppapi: AsyncHttpFetch question

Hi, The motivation for my question is because I am seeing a small leak in my module. My module periodically fetches data using the Async api. When I disable the periodic fetching I don't see a leak (I ensured there is none of my other code is running). I reduced my code base to fetch and forget. I

Re: atscppapi AsyncHttpFetch

Brian, Yes it makes perfect sense. But when I saw the virtual run() l I thought I might me missing something. Getter will do the trick. For now I will implement my own. Sandeep. On Tue, Jan 27, 2015 at 10:03 PM, Brian Geffon wrote: > Unfortunately you cannot access the state_ member because it

Re: atscppapi AsyncHttpFetch

Unfortunately you cannot access the state_ member because it's private in AsyncHttpFetch, I think the best option here might be for us to add a getter method for the dispatch controller. Alternatively, you can just skip inheriting from AsyncHttpFetch and implement the AsyncProvider interface and co