tor/changes/bug5916

  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 nameserver case) and on 0.2.3.9-alpha (for the
      DisableNetwork case).
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. 2012-05-18 18:21:46 +02:00			`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`
Fix a typo in changes/bug5916 2012-05-30 17:18:49 +02:00			`unconfigurable nameserver case) and on 0.2.3.9-alpha (for the`
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. 2012-05-18 18:21:46 +02:00			`DisableNetwork case).`