> To be honest changing sms_trivial to use malloc instead of > apr_sms_malloc is > an easy move (just a few lines to change) so it's probably worth > trying and then seeing what we get...
Massive leakage :) Remember how the apr_sms_reset code works; it does not have to traverse and destroy all children since they all use the memory from that sms. > BTW, I'm impressed by the amount of traffic this has generated. Exactly > what I hoped it would do! > > I guess also I'm wondering if we should apply my patch. For all > the reasons > given it's not ideal, but it's a starting point, and if in 2 > weeks it looks > totally different, well, no bother, but at least it lets everyone > work on it > with a minimum of fuss... Opinions? 3 +1's and I'll commit while I'm in > Pheonix (got a nice connection) Don't know if it counts, but +1 :) > david Sander
