Topic: Version 0.6.0 released - page 2. (Read 10482 times)

The blockchain download speed is soo much faster now!

<3

You can just install but always (on this ver or any verion) make a backup of wallet.dat before upgrading.

Any issues upgrading or can I just install and open w/o loss?

Github doesnt seem to accept new accounts:  "There were problems creating your account." It gives no further details, so I dont know how to get on there.

The platform is CentOS 5.6 x64.  The cause of the problem is unknown.  It started shortly after 2am CET this morning, and is probably related to whatever has been received around that time (because it worked for almost a day before).  I have posted everything that I have, which is (-debug -printtoconsole).  There was another piece of information which I didnt save unfortunately.  It a crash report after the first crash, and it contained a call stack dump.  The initial cause for the crash was a "free" of invalid memory.  I have another similar box that also crashed tonight, but it did not dump the callstack and it did have less problems to start again.  Therefore the other problems are probably caused by data that has been saved during the initial problematic event, and in fact the first box only came up again after deleting all cached data in .bitcoin/ and in particular the addr.dat file.

So there must be at least three problems, one is that an invalid memory free can be triggered, another one is that the file parsers can bail out fatally when encountering corrupt file content, and the third problem is that normal operation can cause files be filled with such corrupt content.

Let me know what else you need to know from me.

All righty... you're the first person I've heard that from.

Please file bug reports on the github issue tracker. Include enough information so we can reproduce the problem (what platform? what seems to cause the problem? etc) and it might get fixed.

I say "might" because if you're serving up a big mining pool running bitcoind on Windows... well, none of the current core developers work on Windows.

I wonder what is the criteria to become "whitelisted" ?  (one must have been angry for the past six months ?)

@gavin and team:
thanks and keep up the good work, you guys are outstanding!

Good thing you reported this in RC1 to RC5 so it is already fixed..... er wait you didn't?

The devs have been begging for beta testers for a while now. I suggest that you liaise with them to set something up, instead of bashing them without knowing what's up. Perhaps you could join the #bitcoin-dev IRC channel on freenode, and hit up the mailing list, and give them REPRODUCIBLE issues to test and fix.

Calm down.

Gavin Andresen,

Horrible work.  Absolutely NOT impressed.

You have >100 bugs open and yet decide to release on 30-march and FORCE the update for 1-april.  Just two days later.

This release is unstable as hell.  I get crashes.  I get unexpected exits.  And I get failures to restart.


Crashes:
-----------

************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::txn_checkpoint: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in ThreadMessageHandler()


Unexpected exits:
--------------------

04/05/12 11:38:48 sending: inv (73 bytes)
04/05/12 11:38:49 received: addr (31 bytes)
connection timeout
04/05/12 11:38:49 received: addr (31 bytes)
trying connection 200.74.242.32:8333 lastseen=-2.3hrs
04/05/12 11:38:50 received: addr (31 bytes)
04/05/12 11:38

--> Result code: 139


Failures to restart:
--------------------

Loading addresses...
dbenv.open strLogDir=/home/XXX/.bitcoin/database strErrorFile=/home/XXX/.bitcoin/db.log


************************
EXCEPTION: NSt8ios_base7failureE      
CDataStream::read() : end of data      
bitcoin in AppInit()      

--> Result code: 134


What about good Q&A procedures?  What about testing stuff before release ("compiles fine on Win7" is NOT testing)?  What about establishing a stable status quo BEFORE forcing it on people, like for a month/year?


I get 80% orphans with the old version, and I get 95% downtime with the new version.  Great choices, thanks a lot for that.

Okay! Thank you guys!! 

I guarantee you, nothing changed in the fee policy since 0.3.23. Whether a fee is required or not depends on the size and age of the input coins you're using.

For those transactions, it is entirely possible that you wouldn't have paid a fee even with the old client. Fees are usually applied when the transaction is over the size limit, but they also may be waived if the coins have been sitting in your wallet for a sufficient period of time. I'd say don't worry about it.

Well, the behavior in 0.6.0 is different of 0.5.3.
With 0.5.3 (using the same bitcoin.conf) I pay the fees automatically, now, I pay no fees...
How to "restore" the old behavior?!

Fees have always been voluntary, except in case of sending very small outputs, or using too recent/too small inputs, as a means for spam protection on the network. The details of this policy have not been changed since 0.3.23.

Mmmm... I don't use GUI... only bitcoind in Ubuntu Linux...

So, I just need to add the option:

paytxfee=?.??

at ~/.bitcoin/bitcoin.conf ?

I would like to have it dynamic as before... Not a fixed fee. But how?!

In the settings, you'll find a checkbox there! Or with a supplied flag, -paytxfee=.

Dia

Hi!

 Where is the TX-fees?!?!

 I just send 50.00 and 10.00 and for both transactions, the fee = 0.00 !!

 But, with the previous versions, the client automatically put a default fee there...

 I would like to pay the fees!! how to enable it again?!

Thanks!
Thiago

I understand why we went back to absolute and agree it needed to be done for the newbs.. What I was suggesting is an option to switch to relative in the options screen.

How about this?  https://github.com/bitcoin/bitcoin/pull/1030

Show the number of blocks left to download, instead of a percentage.

The reason the display was changed back to being absolute rather than relative was for new users.  Suppose a new user installs the client, downloads half the blocks, sees it take hours to go from 0% to 50%, then quits and restarts.  With the relative scheme, the display would start back to 0% again, and the user may well think that it was starting from the beginning, and give up on the whole idea.

See the discussion here: https://github.com/bitcoin/bitcoin/issues/753