Leaking cached_resolve_t
02:45 < phobos> 1169451822: 21908908: total-size count source 02:45 < phobos> 1169451822: 21908908: 73920 231 dns.c:685 02:45 < phobos> 1169451822: 21908908: 168 2 bn_lib.c:328 02:45 < phobos> 1169451822: 21908908: 48 2 bn_lib.c:295 02:45 < phobos> 1169451822: 21908908: 74136 235 Total of 3 02:47 < nickm> huh. 02:47 < nickm> Okay, that's easy to fix, I think. 02:47 < nickm> Is that svn, or 0.1.2.6, or other? 02:47 < phobos> 0.1.2.6-alpha 02:48 < phobos> i'm testing svn now 02:49 < phobos> or i can wait for a fix 02:49 < phobos> either way 02:49 < nickm> hmm. 02:49 < phobos> err, either way i've already destroyed my tor server uptime and stability 02:49 < nickm> actually, less trivial. 02:49 < nickm> I'll have to think a touch. 02:49 < nickm> That's definitely lost? 02:50 < nickm> and not, say, "reachable"?
In 0.1.2.6, this line is: resolve = tor_malloc_zero(sizeof(cached_resolve_t)); in dns_resolve().
So apparently we have some cached_resolve_t items that are never freed.
[Automatically added by flyspray2trac: Operating System: All]