X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 126803858D28 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=ispras.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=ispras.ru MIME-Version: 1.0 Date: Fri, 08 Apr 2022 00:53:31 +0300 From: Alexey Izbyshev To: cygwin AT cygwin DOT com Subject: Deadlock of the process tree when running make User-Agent: Roundcube Webmail/1.4.4 Message-ID: <9388316255ada0e0fcb2d849cce5a894@ispras.ru> X-Sender: izbyshev AT ispras DOT ru X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_00, DOS_RCVD_IP_TWICE_B, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Cygwin" Hi, I'm using 32-bit Cygwin 3.3.4 on 64-bit Windows 10 21H2. When running parallel make (for testing my project), very rarely I get the whole process tree hanging at some seemingly random point. An example of such a tree: make-+-make-+-bash---find | |-bash---find | |-bash---find | |-bash---find | |-bash---find | `-bash---javac `-make-+-bash---bash---bash---readlink `-bash---bash---bash-+-grep `-grep (In the above tree, javac is the zombie parent of a native javac, and the latter doesn't exist at this point). I got such hang two times while running make in a loop for several days. ProcessHacker shows that all leaf processes are single-threaded and are stuck on WaitForSingleObject(). I've skimmed git log of cygwin-3_3-branch after cygwin-3_3_4-release, but couldn't find anything that seems definitely related. Has anybody seen something like this? Is there any way I can get useful data for diagnosing this hang from the process tree that I currently have hanging (I'm going to keep it for now)? Otherwise, what would be the best strategy? Thanks, Alexey -- 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