sudheerv commented on pull request #6925: URL: https://github.com/apache/trafficserver/pull/6925#issuecomment-646429084
> I'm fine with adding the assert, but what do we do on release build? use-after-free can still happen. Yeah, I’ve been debating whether it should be ink_release_assert(). I’ve been running with null pointer protection and release assert in prod to catch such corruption in prod for the last few days. Didn’t really catch anything from that directly but ASAN caught some memory corruptions which may be the root cause for this. I’m okay to switching this to release assert if that’s what you prefer. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
