From: "Elfyn McBratney" <elfyn-cygwin@exposure.org.uk>
To: "cygwin" <cygwin@cygwin.com>
Subject: Re: 1.3.19: fork() strange memory leak under W2K
Date: Sat, 08 Feb 2003 23:26:00 -0000 [thread overview]
Message-ID: <010401c2cfc9$a8bed510$6b7c86d9@webdev> (raw)
In-Reply-To: <83040F98B407E6428FEC18AC720F5D73E501F1@exchange.tropicnetworks.com>
> Some time ago, when I was using at home 1.3.18 version of
> CygWin under Windows 2000 Workstation + SP3, I
> discovered that every command execution lead to some memory
> leak. It's especially noticeably when I try to run large
> scripts (like "configure") - the memory loading (as viewed
> in Task Manager) grow to its physical size and next I
> get message like this:
>
> 0 [main] sh 35620 sync_with_child: child 35636(0xDC)
> died before initialization with status code 0x80
> 6847 [main] sh 35620 sync_with_child: *** child state
> waiting for longjmp
> ./../ltconfig: fork: Resource temporarily unavailable
>
> After this, any process can't be started without rebooting
> (or killing other process).
>
> Recently, I upgraded my system to Windows 2000 Server +
> SP3 (with total precleanup) and CygWin 1.3.19, but problem is
> there as before. :(
>
> [...]
>
> It's very strange, but all this works nice at my work on
> computer with Windows 2000 Workstation + SP3! My home
> computer hardware is AMD Duron 800 MHz, Abit KT7A
> Motherboard, 256 MB RAM; at work Celeron 800 MHz, Acorp i815
> Motherboard, 128 MB RAM. The difference is also in the
> filesystems: FAT32 at home and NTFS at work.
>
> [...]
Sorry for the "me too" on this, but well Me too ;-)
I am unable to test this on a FAT32 partition as I don't have one on my or
any other system I work with. Perhaps you could provide strace output? Igor
gave some very good pointers ("Re: rcs ci and co hang") on this list a few
days ago, although it's not the same issue, you could use some of the
instructions to gather the strace output and send some/it to the list.
If it does reach an outrageous size, or you're not to sure what it means, I
don't mind if you send it to me off-list and I'll take a gander (compressed
ofcourse ;-)...
Regards,
Elfyn McBratney
elfyn@exposure.org.uk
www.exposure.org.uk
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-02-08 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 22:48 Rolf Campbell
2003-02-08 23:26 ` Elfyn McBratney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-08 22:16 Victor Antonovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='010401c2cfc9$a8bed510$6b7c86d9@webdev' \
--to=elfyn-cygwin@exposure.org.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).