X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:in-reply-to:references:mime-version :content-type:content-transfer-encoding:subject:from:date:to :message-id; q=dns; s=default; b=AoZH1p2iqQvdUb4CWv35Iijd/CpuKOE cliFw5JsT5jjJSZxquQB/9VD6yRpN3Dp9J2uS1bd7ldvlZLUVbtjhKi9x02yO5rF UefMUcJTi8jfY5P825gTnqepOJLd68pW0pqrj2ZZX4DqDcyhhSx8xAp8Zx3AKZuI SfsJTzMoghjk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:in-reply-to:references:mime-version :content-type:content-transfer-encoding:subject:from:date:to :message-id; s=default; bh=X9TjZAwEiG2VE1NSDes8AXE2tSs=; b=cfQ4A el3SGpFjxsNNCGWPcZg3X+/rEcyHaQjH+0HvXBMeFJGb2CSOL8z0bV1UI75kwTou ZVnW2MWl+anmDc0TVCEQPO99AnCg/bLplOor38/62QzcrjlKcGjnGP4ep9o/H2ZS 0KKRY82/8sMMrmg8bkwFmYnz/pA6zbflwgYanI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: nm46-vm2.bullet.mail.ne1.yahoo.com X-Yahoo-SMTP: BVtuZFiswBBG504e4DQIhRExpptF4H0nV7E7 User-Agent: K-9 Mail for Android In-Reply-To: <160B707E-6BFC-4AD5-BBE0-56F810C13C94@etr-usa.com> References: <192042331 DOT 20150611220629 AT morauf DOT de> <160B707E-6BFC-4AD5-BBE0-56F810C13C94 AT etr-usa DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Subject: Re: cygwin memory leak From: Ian Lambert Date: Mon, 15 Jun 2015 12:31:23 -0400 To: The Cygwin Mailing List Message-ID: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5FGYSo5009616 > >> The taken memory is never >> freed until os restart. > >I don’t think Cygwin could do that even if it wanted to, given that you >don’t have any Cygwin services running. Once the last Cygwin process >dies, the OS *will* release the memory it was holding. It does, however, seem vulnerable to fork bombs, like: $cat dontdothis #!/bin/sh while (( 1 )); do /bin/true ./dontdothis & done :) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple