X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Marc Compere Subject: slow bash spawn Date: Sun, 18 Mar 2007 13:27:31 +0000 (UTC) Lines: 20 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com The recent setup.exe update has caused bash.exe to have startup times approx. 10x longer than before. sh.exe starts pretty quickly but bash.exe via cygwin.bat takes ~30 seconds to start. Took just a couple of seconds before. Cpu is nowhere near pinned, hovering around 3% or 5%. Each bash process spawn from within bash takes a long time as well making ./configure and make take a lot longer than before. Similar problem here: http://www.nabble.com/Slow-compile-issue-with-cygwin- make-since-v1.5.17-t3235008.html Interestingly enough, sh.exe spawns relatively quickly. Anyone else had similar problems or, more importantly, found a solution? Running XP sp2 on a fresh, plain vanilla cygwin install. antivirus is not the problem as bash started just fine on cygwin release just a few weeks ago. TIA, Marc -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/