From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.4rc1 known bugs
Date: Sat, 3 Sep 2011 20:13:14 -0400 [thread overview]
Message-ID: <CABsx9T1juB-0hr9NW=PoO5eh_Aqhzkiv3tnXTSTsjBKiy4y0JA@mail.gmail.com> (raw)
Quick status update on 0.4; I probably won't have time to tackle these
properly before Tuesday:
+ sipa found what looks like a deadlock between the addr-handling and
IRC-join-handling code.
+ UukGoblin reports a deadlock problem on a bitcoind handling getwork requests.
If you want to get more familiar with the bitcoin code and you have a
lot of patience, tracking down deadlocks a great way to do it.
+ ArtForz found a performance bug with transactions that have
thousands of inputs and outputs on the solidcoin test network.
(not as big an issue for bitcoin due to fees being based on
transaction size, but still worrying)
--
--
Gavin Andresen
next reply other threads:[~2011-09-04 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 0:13 Gavin Andresen [this message]
2011-09-04 2:43 ` Matt Corallo
2011-09-05 7:25 ` Michael Grønager
2011-09-05 12:42 ` Luke-Jr
2011-09-05 12:47 ` Michael Grønager
[not found] ` <20110904115926.GA16476@ulyssis.org>
2011-09-06 11:55 ` Pieter Wuille
2011-09-06 17:59 ` Gavin Andresen
2011-09-06 20:55 ` Luke-Jr
2011-09-07 15:07 ` Gavin Andresen
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='CABsx9T1juB-0hr9NW=PoO5eh_Aqhzkiv3tnXTSTsjBKiy4y0JA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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