diff options
| author | Nick Mathewson <nickm@torproject.org> | 2012-05-18 12:21:46 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2012-05-18 12:21:46 -0400 |
| commit | 4c4dd505be30de996659f9d3496fc88956fcfbf6 (patch) | |
| tree | 6d7fe6218ce2518e272b1537614bc0cf0aa8e928 /changes/bug5916 | |
| parent | c1da29e22d138bb30b6ade452aa0e0321330efe3 (diff) | |
| download | tor-4c4dd505be30de996659f9d3496fc88956fcfbf6.tar.gz tor-4c4dd505be30de996659f9d3496fc88956fcfbf6.zip | |
Fix a hard-to-trigger memory leak in launch_resolve
To hit this leak, you need to be a relay that gets a RESOLVE request
or an exit node getting a BEGIN or RESOLVE request. You must either
have unconfigured (and unconfigurable) nameservers, or you must have
somehow set DisableNetwork after a network request arrived but
before you managed to process it.
So, I doubt this is reached often. Still, a leak's a leak. Fix for
bug 5916; bugfix on 0.2.3.9-alpha and 0.1.2.1-alpha.
Diffstat (limited to 'changes/bug5916')
| -rw-r--r-- | changes/bug5916 | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug5916 b/changes/bug5916 new file mode 100644 index 0000000000..0b2ea5df44 --- /dev/null +++ b/changes/bug5916 @@ -0,0 +1,6 @@ + o Minor bugfixes: + - Fix a memory leak when trying to launch a DNS request when the + network is disabled or the nameservers are unconfigurable. Fix + for bug 5916; bugfix on Tor 0.1.2.1-alpha (for the + unconfigurable namesrever case) and on 0.2.3.9-alpha (for the + DisableNetwork case). |