X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: random "fork: Resource temporarily unavailable" Date: Thu, 22 Jun 2006 06:35:04 -0700 Message-ID: <251D2B65F6DECE47A69C7C3AB504D72FB75C9A@namail2.corp.adobe.com> in-reply-to: <44983DAC.2030008@cygwin.com> From: "Mark Bartel" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Note-from-DJ: This may be spam Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k5MDZRdt026762 Larry Hall wrote: > Mark Bartel wrote: > > Larry Hall wrote: [deletia] > > This sounds like the same issue I was encountering. I can reproduce it > > on demand with: > > > > mbartel AT mbartel-t60p ~ > > $ find * -type f -exec grep foo {} /dev/null \; > > 6 [main] find 435884 fhandler_dev_zero::fixup_mmap_after_fork: > > requested 0x480000 != 0x0 mem alloc base 0x480000, state 0x2000, size > > 1040384, Win32 error 487 > > 272 [main] find 435884 C:\cygwin\bin\find.exe: *** fatal error - > > C:\cygwin\bin\find.exe: *** recreate_mmaps_after_fork_failed > > 13 [main] find 434720 child_info::sync: wait failed, pid 435884, > > Win32 error 0 > > 344 [main] find 434720 fork: child -1 - died waiting for longjmp > > before initialization, retry 10, exit code 0x1000000, errno 11 > > find: cannot fork: Resource temporarily unavailable > > > > mbartel AT mbartel-t60p ~ > > $ > > > > Unfortunately, it is more than just annoying in my case, as it happens > > all the time. I had to buy MKS Toolkit to get on with my job. > > > So are you saying you still see the problem after using a recent snapshot > ? Yes, the error above is with the 20060529 snapshot. However, yet another person who has encountered this problem emailed me with a workaround, which seems to resolve the issue in my case. He had encountered the problem himself, and he found http://aslongas.pe.kr/tt/ which says to turn off the "Logitech Process Monitor" service, installed with Logitech webcam software. -Mark -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/