From: Gavin Andresen <gavinandresen@gmail•com>
To: Michael Gronager <gronager@ceptacle•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BitcoinQt eating 100% CPU
Date: Thu, 23 Feb 2012 15:26:40 -0500 [thread overview]
Message-ID: <CABsx9T03coJ6DdAUqgJGngu1GU1qm=J-qGLKR1VTipkSOPWEaA@mail.gmail.com> (raw)
In-Reply-To: <3428A99D-3E68-4E06-9DD1-83741C9CDD42@ceptacle.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 786 bytes --]
next prev parent reply other threads:[~2012-02-23 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 20:33 Michael Grønager
2012-02-23 20:02 ` Michael Gronager
2012-02-23 20:26 ` Gavin Andresen [this message]
2012-02-23 20:33 ` Luke-Jr
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='CABsx9T03coJ6DdAUqgJGngu1GU1qm=J-qGLKR1VTipkSOPWEaA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gronager@ceptacle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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