Message-ID: <4FE06ADD.80706@cs.utoronto.ca>
Date: Tue, 19 Jun 2012 08:04:45 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Cygwin unstable as hell on Windows7 =?UTF-8?B?NjRiaXTigI8=?=
References: <4FE0596F.4060702@roularta.be> <4FE05A98.9050704@samsung.com>
In-Reply-To: <4FE05A98.9050704@samsung.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 19/06/2012 6:55 AM, Fedin Pavel wrote:
> On 19.06.2012 14:50, Gerard H. Pille wrote:
>> Since my system was replaced by one running Windows 7 on an Intel 
>> Core I5, I may call myself lucky if I can work for an hour.
> Works fine here. May be your hardware is flaky ? RAM for example... 
> Cygwin loads up the system quite well, especially upon fork().
>
That or a particularly virulent BLODA... The fact that shells crash 
while idle hints strongly that the blame lies outside Cygwin; if other 
random apps (particularly the memory hogs like web browsers and email 
clients) aren't crashing, that points to BLODA rather than bad RAM. I'd 
also do a virus scan: some malware monitors the process list and kills 
anything it thinks might be used to detect or attack it; command prompts 
usually rank high on the hit list.

(I'm running 64-bit win7 on a core I5 without troubles for the last 18 
months or so)

Ryan


--
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