Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gavinandresen@gmail.com>) id 1S0fFW-0005yq-TP for bitcoin-development@lists.sourceforge.net; Thu, 23 Feb 2012 20:26:46 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=gavinandresen@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1S0fFW-0000ac-5x for bitcoin-development@lists.sourceforge.net; Thu, 23 Feb 2012 20:26:46 +0000 Received: by wgbdr12 with SMTP id dr12so1407367wgb.10 for <bitcoin-development@lists.sourceforge.net>; Thu, 23 Feb 2012 12:26:40 -0800 (PST) Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates 10.180.94.68 as permitted sender) client-ip=10.180.94.68; Authentication-Results: mr.google.com; spf=pass (google.com: domain of gavinandresen@gmail.com designates 10.180.94.68 as permitted sender) smtp.mail=gavinandresen@gmail.com; dkim=pass header.i=gavinandresen@gmail.com Received: from mr.google.com ([10.180.94.68]) by 10.180.94.68 with SMTP id da4mr5907153wib.22.1330028800146 (num_hops = 1); Thu, 23 Feb 2012 12:26:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.94.68 with SMTP id da4mr4826053wib.22.1330028800104; Thu, 23 Feb 2012 12:26:40 -0800 (PST) Received: by 10.223.121.197 with HTTP; Thu, 23 Feb 2012 12:26:40 -0800 (PST) In-Reply-To: <3428A99D-3E68-4E06-9DD1-83741C9CDD42@ceptacle.com> References: <81E27E9B-BD4B-4429-BF91-FED3505CE6D0@ceptacle.com> <3428A99D-3E68-4E06-9DD1-83741C9CDD42@ceptacle.com> Date: Thu, 23 Feb 2012 15:26:40 -0500 Message-ID: <CABsx9T03coJ6DdAUqgJGngu1GU1qm=J-qGLKR1VTipkSOPWEaA@mail.gmail.com> From: Gavin Andresen <gavinandresen@gmail.com> To: Michael Gronager <gronager@ceptacle.com> Content-Type: multipart/alternative; boundary=f46d044286902bd86504b9a77667 X-Spam-Score: -0.9 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.3 AWL AWL: From: address is in the auto white-list X-Headers-End: 1S0fFW-0000ac-5x Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] BitcoinQt eating 100% CPU X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 23 Feb 2012 20:26:47 -0000 --f46d044286902bd86504b9a77667 Content-Type: text/plain; charset=ISO-8859-1 Bitcoin-Qt is now running nicely using around 0.9% CPU. So it seems like > the culprit was indeed line 31: > > if(mq->timed_receive(&strBuf, sizeof(strBuf), nSize, nPriority, d)) > > Others, who have seen similar issues ? > > I can definitely reproduce the issue on my mac. If I recall correctly, the Mac Bitcoin-Qt does not register itself as a bitcoin: URL handler, so the easiest fix for the 0.6 release would be to just never launch the ipcThread #ifdef Q_WS_MAC -- -- Gavin Andresen --f46d044286902bd86504b9a77667 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <br><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Bitcoin-Qt is now running nicely using around 0.9% CPU. So it seems like th= e culprit was indeed line 31:<br> <div class=3D"im"><br> if(mq->timed_receive(&strBuf, sizeof(strBuf), nSize, nPriority, d))<= br> <br> </div>Others, who have seen similar issues ?<br><br></blockquote><div><br><= /div><div>I can definitely reproduce the issue on my mac.</div><div><br></d= iv><div>If I recall correctly, the Mac Bitcoin-Qt does not register itself = as a bitcoin: URL handler, so the easiest fix for the 0.6 release would be = to just never launch the ipcThread #ifdef Q_WS_MAC</div> <div><br></div></div><div><br></div>-- <br>--<br>Gavin Andresen<br><br> --f46d044286902bd86504b9a77667--