Author

Topic: Bug in latest git (Read 1095 times)

member
Activity: 81
Merit: 1002
It was only the wind.
September 20, 2013, 05:06:43 PM
#10
Ding ding! indeed thats informative.

As a workaround, set a rpcuser / rpcpassword and server=1 in your config. I am 92% confident that the issue will go away for you.


You were right, no more crash.
member
Activity: 81
Merit: 1002
It was only the wind.
September 19, 2013, 08:58:41 PM
#8
Here, this ought to help:

Code:
bitcoin-qt: src/bitcoinrpc.cpp:863: void RPCRunLater(const string&, boost::function, int64): Assertion `rpc_io_service != __null' failed.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe813b700 (LWP 29835)]
0x00007ffff48773d9 in raise () from /usr/lib/libc.so.6
member
Activity: 81
Merit: 1002
It was only the wind.
September 13, 2013, 08:06:05 PM
#7
It's 100% reproducible for me so far, used a timeout of 600, linux x86_64, and grue, you have to have an encrypted wallet.
Does it crash instantly or after 10 minutes?

Instantly. Also, I used it on mainnet.
staff
Activity: 4284
Merit: 8808
September 19, 2013, 10:13:48 PM
#5
Ding ding! indeed thats informative.

As a workaround, set a rpcuser / rpcpassword and server=1 in your config. I am 92% confident that the issue will go away for you.
staff
Activity: 4284
Merit: 8808
September 13, 2013, 07:44:30 PM
#4
It's 100% reproducible for me so far, used a timeout of 600, linux x86_64, and grue, you have to have an encrypted wallet.
Does it crash instantly or after 10 minutes?
staff
Activity: 4284
Merit: 8808
September 13, 2013, 03:33:39 PM
#3
No crash for me in bitcoin-qt on linux x86_64 built from current git on testnet when unlocking. What time out did you give it? is it 100% reproducible for you?
legendary
Activity: 2058
Merit: 1452
September 13, 2013, 02:18:35 PM
#2
bug reports should be reported here: https://github.com/bitcoin/bitcoin/issues

also, I was not able to replicate the issue with 0.8.5 (unecrypted wallet used)
member
Activity: 81
Merit: 1002
It was only the wind.
September 13, 2013, 02:09:49 PM
#1
NaN.
Jump to: