public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kate Deplaix <kit-ty-kate@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel
Date: Thu, 29 Feb 2024 18:19:45 +0000	[thread overview]
Message-ID: <CWXP265MB13688A1AAB4643076818482ABC5F2@CWXP265MB1368.GBRP265.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]

  *
Hi,

I've been using Cygwin for the past year without any issues, however today I upgraded to Cygwin 3.5.1 from 3.4 and noticed a consistent freeze of every Cygwin processes happening, and there is no way to call a new Cygwin process anymore (e.g. even the terminal doesn't show up) without logging off my user session and logging back on.

Other users and coworkers of mine have noticed this happening too the past couple days (first recorded break was on the 25th, with I presume, Cygwin 3.5.0).

To reproduce this:

  *
make sure you have a fresh installed of cygwin 3.5.1
  *
install the following packages: autoconf, make, patch, curl, mingw64-x86_64-gcc-g++, mingw64-i686-gcc-g++
  *
curl -LO https://github.com/ocaml/opam/releases/download/2.2.0-beta1/opam-full-2.2.0-beta1.tar.gz
  *   tar xvf opam-full-2.2.0-beta1.tar.gz
  *   cd opam-full-2.2.0-beta1
  *   make cold

  *
  *
At some point of the make process, one job will infinit loop (taking 100% of one core), while the rest of the mingw jobs will idle and never finish. After some time Cygwin Terminal isn't responsive anymore, and I'm not able to open another one or to spawn any other processes that are relying on the cygwin dll. I was able to observe this behaviour every time i tried consistently.
  *

It was noticed that passing -j1 to all the calls to make in the shell/bootstrap-ocaml.sh script fixes this issue, so I'm guessing this is some kind of multicore scheduling issue.

Given it is the core of our project (the compiler) that makes the whole system freeze and that we were hoping to release this project soon, whose main item in the changelog is Windows support using Cygwin, it is somewhat vital for us for this to be fixed, and while we don't know much of the Cygwin internals/codebase we're ready to help in any ways we can.

Kind regards,
Kate

             reply	other threads:[~2024-02-29 18:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 18:19 Kate Deplaix [this message]
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
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=CWXP265MB13688A1AAB4643076818482ABC5F2@CWXP265MB1368.GBRP265.PROD.OUTLOOK.COM \
    --to=kit-ty-kate@outlook.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).