From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126319 invoked by alias); 10 Aug 2015 16:01:55 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 126309 invoked by uid 89); 10 Aug 2015 16:01:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Aug 2015 16:01:53 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id B3B0CA805A1; Mon, 10 Aug 2015 18:01:50 +0200 (CEST) Date: Mon, 10 Aug 2015 16:01:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: commands spends time in cygheap_user Message-ID: <20150810160150.GD13029@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1437114390582-119766.post@n5.nabble.com> <1438937297149-120365.post@n5.nabble.com> <20150807090646.GB12475@calimero.vinschen.de> <1438977081850-120377.post@n5.nabble.com> <20150810084019.GB1559@calimero.vinschen.de> <1439208020687-120403.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TybLhxa8M7aNoW+V" Content-Disposition: inline In-Reply-To: <1439208020687-120403.post@n5.nabble.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-08/txt/msg00139.txt.bz2 --TybLhxa8M7aNoW+V Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2816 On Aug 10 05:00, mku wrote: > Oh, sorry. I did a fresh 2.2 install to avoid side effects from my previo= us > updated one and forgot to modify the nsswitch.conf. After correcting it, = the > result now is the same from the time aspect but loading of the net dlls h= ave > now disappeared as expected. > +++ 8< ----- > 280 44318 [main] ls 181944 client_request::make_request: cygserver > un-availa > --- Process 181944 loaded C:\Windows\SysWOW64\advapi32.dll at 75400000 > --- Process 181944 loaded C:\Windows\SysWOW64\msvcrt.dll at 76CB0000 > --- Process 181944 loaded C:\Windows\SysWOW64\sechost.dll at 76A00000 > --- Process 181944 loaded C:\Windows\SysWOW64\rpcrt4.dll at 75300000 > --- Process 181944 loaded C:\Windows\SysWOW64\sspicli.dll at 750C0000 > --- Process 181944 loaded C:\Windows\SysWOW64\cryptbase.dll at 750B0000 > --- Process 181944 thread 186236 created > 4525052 4569370 [main] ls 181944 cygheap_user::ontherange: what 2, pw > 0x612FFCF0 > 302 4569672 [main] ls 181944 cygheap_user::ontherange: HOME is already = in > the > --- 8< ----- > I don't know how the delta time is calculated. As the time lag is always > printed after loading the dlls, it may be that the log message is printed > after the logged step has been completed. If that is true, the time lag m= ay > occur while loading one of the dlls or creating the thread. >=20 > As I mentioned before the same command repeated one second again shows > normal behaviour (0.406s). > +++ 8< ----- > 106 20307 [main] ls 201132 client_request::make_request: cygserver > un-availa > --- Process 201132 loaded C:\Windows\SysWOW64\advapi32.dll at 75400000 > --- Process 201132 loaded C:\Windows\SysWOW64\msvcrt.dll at 76CB0000 > --- Process 201132 loaded C:\Windows\SysWOW64\sechost.dll at 76A00000 > --- Process 201132 loaded C:\Windows\SysWOW64\rpcrt4.dll at 75300000 > --- Process 201132 loaded C:\Windows\SysWOW64\sspicli.dll at 750C0000 > --- Process 201132 loaded C:\Windows\SysWOW64\cryptbase.dll at 750B0000 > --- Process 201132 thread 201240 created > 9195 29502 [main] ls 201132 cygheap_user::ontherange: what 2, pw > 0x612FFCF0 > 95 29597 [main] ls 201132 cygheap_user::ontherange: HOME is already = in > the > --- 8< ----- > If you wait a longer period (e.g. 5 minutes), the first (longer) behaviour > is shown. > As this time lag is not seen with Version 1.7.28 on the same machine, I > assume that it has come with Version 2.2. Well, it might have been introduced by *any* version later than 1.7.28. It's very unlikley that this has been introduced by 2.2.0. From the above output it's not clear where it hangs. I'll try to reproduce it later this week. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --TybLhxa8M7aNoW+V Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVyMruAAoJEPU2Bp2uRE+gRYUP/29ks60cuVcUB3jx133lwFOt hfFmTudyz8Lv7q9b2NjGjmA+SjDAvYZ4kQiF1v4AZfONOzgbKMzxOavPXYeKO47H fV3R7s+OYyKczeAMSZ66M5tj0Ky9kTxaRHNBkB5FDuiGnLQdQUSlCFKCk/fNPccD VB6oyxW6JC/IEr1CKiQjmo6wYTu5GJwJNJh6u//Ro1tnc7UU5wFrZpbR6ZQE89bT HmHtAtQAs9AL9yAtWvzs1YDISqwVj/FGauKT7Z113ilN+kRC/gtK6DsV+MClkAES ePFwMnsy0JZlWEbyL65rEWaScS27NLUoMg4toJfOIPp0XKn5rS8prNQcrDI5NwVr gY1YMVqFnCBkItPYHQOf8kO2CFk+C6ddN51zSM1Bktf+rAAaTjdA0TLoAICGRpC8 +2XIAa+WSLD5r8wmfoh/IReOdZUGtUsJPnaIkeT99AOCBW10cRE3EClFsBtmfGrm vJnHw4LDSR9+8P0SkInbHxGA8NOyPZh1/3NGUFqXoUxi7UZ4WzgyrJ+SSaJTyhoK venSccn9zLn7CpqJPtEZ1Q5X/yhk6pFJ4d+htYsU1d6k/Nj5iJNsV9abCIq18sgU hNKlFV5SZP2wU5vyWli0wmIwt2BSco2suKQxveK0L+MJne3oMzV+Q2sO4vSnokf+ 5TjyqTLnY7qtaeEYO9D/ =qdfh -----END PGP SIGNATURE----- --TybLhxa8M7aNoW+V--