public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Cedric Blancher <cedric.blancher@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel
Date: Mon, 4 Mar 2024 20:54:35 +0100	[thread overview]
Message-ID: <CALXu0UcUn6OBMEmWgvsUvHBntwkv_18Lj92iYcDPxKom9ew-gQ@mail.gmail.com> (raw)
In-Reply-To: <E58B42EA-E675-4B25-B3EF-241702045059@unified-streaming.com>

Same here building gcc with the msnfs41client NFSv4.1 filesystem
driver (https://sourceforge.net/p/ms-nfs41-client/mailman/message/58741244/),
make -j8 and make -j128 builds now succeed again.

Is a Cygwin 3.5.x backport required?

Ced

On Mon, 4 Mar 2024 at 20:38, Dimitry Andric via Cygwin
<cygwin@cygwin.com> wrote:
>
> Same here, did a bunch of make -j8 builds, and with 3.6.0-0.71.gb160b690b6ac they now complete without any hangs.
>
> Thanks for the quick fix!
>
> -Dimitry
>
> > On 4 Mar 2024, at 16:58, Kate Deplaix via Cygwin <cygwin@cygwin.com> wrote:
> >
> > After testing that version without interruption for the past 3 hours on test cases that would've failed before, I can happily say it looks like it's fixed!
> >
> > Thank you so much!!
> > ________________________________
> > From: Cygwin <cygwin-bounces+kit-ty-kate=outlook.com@cygwin.com> on behalf of Takashi Yano via Cygwin <cygwin@cygwin.com>
> > Sent: 04 March 2024 12:06
> > To: cygwin@cygwin.com <cygwin@cygwin.com>
> > Subject: Re: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel
> >
> > On Mon, 4 Mar 2024 20:00:13 +0900
> > Takashi Yano via Cygwin wrote:
> >> On Sun, 3 Mar 2024 13:07:11 +0900
> >> Takashi Yano wrote:
> >>> On Sat, 2 Mar 2024 11:49:36 +0000
> >>> Kate Deplaix wrote:
> >>>> I'm running cygwin on baremetal on an Intel i5-750 (4 cores), with 7GB of RAM and with an up-to-date Windows 10.
> >>>
> >>> Thanks for the information. I could reproduce the problem with
> >>> Core i5 M 540 + 8GB RAM machine.
> >>>
> >>> Let consider how to debug.
> >>
> >> I found the cause. I'll push the patch shortly.
> >> Thanks!
> >
> > Please try:
> > cygwin 3.6.0-0.71.gb160b690b6ac (TEST)
> >
> > --
> > Takashi Yano <takashi.yano@nifty.ne.jp>
> >
> > --
> > Problem reports:      https://cygwin.com/problems.html
> > FAQ:                  https://cygwin.com/faq/
> > Documentation:        https://cygwin.com/docs.html
> > Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
> >
> > --
> > Problem reports:      https://cygwin.com/problems.html
> > FAQ:                  https://cygwin.com/faq/
> > Documentation:        https://cygwin.com/docs.html
> > Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple



-- 
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur

  reply	other threads:[~2024-03-04 19:55 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
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 [this message]
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=CALXu0UcUn6OBMEmWgvsUvHBntwkv_18Lj92iYcDPxKom9ew-gQ@mail.gmail.com \
    --to=cedric.blancher@gmail.com \
    --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).