From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel
Date: Sat, 2 Mar 2024 13:41:04 +0900 [thread overview]
Message-ID: <20240302134104.1696af5869b62727e4fe8dee@nifty.ne.jp> (raw)
In-Reply-To: <CWXP265MB13686F1A651D9D99F6F03276BC5E2@CWXP265MB1368.GBRP265.PROD.OUTLOOK.COM>
On Fri, 1 Mar 2024 17:48:52 +0000
Kate Deplaix wrote:
> Hi,
>
> Using cygwin 3.6.0-0.66.gc77a5689f7bd I was indeed unable to reproduce the issue.
Thanks for tesing.
> However I'm getting a related but slightly different issue now, where a subprocess randomly (but quite reliably over the whole compilation process) fails with make -j (works fine with -j1 once again)
>
> Luckily i was able to make a really small test-case this time:
> Using MinGW 11.4.0 with the following test.c file:
>
> #define UNICODE
> #define _UNICODE
>
> #include <process.h>
> #include <stdio.h>
>
> int main() {
> int ret = _wsystem(L"x86_64-w64-mingw32-gcc -dumpversion");
> if(ret != 0) printf("FOUND %d\n", ret);
> }
>
> compile using: x86_64_w64-mingw32-gcc ./test.c
> and run using: for i in $(seq 1 100) ; do ./a & done
Thanks for the test case. I tried this test case, however,
I cannot reproduce the second problem, i.e. all 100 processes
exited normally.
To increase system load, I also tried:
#define UNICODE
#define _UNICODE
#include <process.h>
#include <stdio.h>
int main(int argc, char *argv[]) {
wchar_t buf[1024];
swprintf(buf, 1024, L"x86_64-w64-mingw32-gcc test.c -o %s", argv[1]);
int ret = _wsystem(buf);
if(ret != 0) printf("FOUND %d\n", ret);
}
and
#!/bin/sh
for i in $(seq 1 200); do ./a.exe $i & done
but, no error was found...
How many cpu cores and how much memory does your system have?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2024-03-02 4:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 18:19 Kate Deplaix
2024-02-29 21:34 ` Kevin Schnitzius
2024-02-29 23:55 ` jojelino
2024-02-29 23:57 ` jojelino
2024-03-01 4:31 ` jojelino
2024-03-01 0:25 ` Takashi Yano
2024-03-01 10:21 ` Takashi Yano
2024-03-01 13:02 ` Takashi Yano
2024-03-01 15:26 ` David Allsopp
2024-03-01 17:48 ` Kate Deplaix
2024-03-02 4:41 ` Takashi Yano [this message]
2024-03-02 11:49 ` Kate Deplaix
2024-03-03 4:07 ` Takashi Yano
2024-03-04 11:00 ` Takashi Yano
2024-03-04 12:06 ` Takashi Yano
2024-03-04 12:26 ` Dimitry Andric
2024-03-04 15:58 ` Kate Deplaix
2024-03-04 19:38 ` Dimitry Andric
2024-03-04 19:54 ` Cedric Blancher
2024-03-04 22:23 ` Dimitry Andric
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=20240302134104.1696af5869b62727e4fe8dee@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).