enabler_first_clarification() memory leak
Reply To cazfi
Other functions do req_to_fstring() calls with similar pattern.
It's not the pattern that is used in req_to_fstring() calling. It's the fact that req_to_fstring() cannot be used without leaking memory as the API is currently designed.
Changes to req_to_fstring() itself have been badly backported to S3_0 patch (lacking the astr initialization, function header updates).
Reply To cazfi
Changes to req_to_fstring() itself have been badly backported to S3_0 patch (lacking the astr initialization, function header updates).
- Fixed
As a server side memory leak, I want to fix these in S2_6 too. Reopening for that part...
Valgrind reports minor leak in S3_0 that comes from the req_to_fstring() call within enabler_first_clarification(). Other functions do req_to_fstring() calls with similar pattern.