Startup crash in 0.10.0rc1: "An invalid argument was supplied" #5560

1. 
   patrikr commented at 12:23 AM on December 29, 2014: none

   0.10.0rc1 crashed with the following exception on every startup:

   EXCEPTION:   
   N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
   An invalid argument was supplied       
   C:\programs\bitcoin-0.10.0rc1\bitcoin-qt.exe in Runaway exception
   

   I was able to bypass the error by commenting out the following lines in bitcoin.conf:

   #rpcuser=something
   #rpcpassword=something_else
   #server=1
   

   OS: Windows XP

2. 
   patrikr commented at 2:21 AM on December 29, 2014: none

   Forum user reporting the same bug: https://bitcointalk.org/index.php?topic=906820.msg9964634#msg9964634

3. laanwj added this to the milestone 0.10.0 on Dec 29, 2014
4. 
   laanwj commented at 8:45 AM on December 29, 2014: member

   Which argument is it exactly that triggers this? If it is e.g. the rpcpassword, can you try different values to see if there's some symbol that triggers a parsing error?

5. 
   patrikr commented at 1:37 PM on December 29, 2014: none

   Doing some more testing... There seems to be plenty of GUI bugs in this version. For example, when I uncommented the "server=1" line but not the others, I got both the startup and shutdown splash windows at the same time, followed by a crash. Once the process locked up completely on the shutdown splash, and once the main window failed to appear, even though blocks were being downloaded in the background.

   Anyway, the following bitcoin.conf causes the "invalid argument" crash every single time:

   rpcuser=x
   rpcpassword=y
   server=1
   

   This one does not:

   rpcuser=x
   rpcpassword=y
   #server=1
   

6. laanwj added the label Windows on Dec 29, 2014
7. 
   laanwj commented at 2:48 PM on December 29, 2014: member

   @diapolo this seems like an issue on windows only, have you ever encountered it?

8. 
   laanwj commented at 2:53 PM on December 29, 2014: member

   May have to do with the lack of IPv6 support on windows XP. As it only triggers with server enabled it may have to do with RPC trying to bind on that. Can you try adding explicit bind command for only IPv4 localhost to your configuration file, ie add both of these:

   rpcbind=127.0.0.1
   rpcallowip=127.0.0.1
   

9. 
   patrikr commented at 2:58 PM on December 29, 2014: none

   OK, I tried the following bitcoin.conf, it works. (No crash.)

   rpcuser=x
   rpcpassword=y
   server=1
   rpcbind=127.0.0.1
   rpcallowip=127.0.0.1
   

10. 
    laanwj commented at 3:16 PM on December 29, 2014: member

    Thanks for confirming.

11. 
    laanwj commented at 4:39 PM on December 30, 2014: member

    Should be fixed by #5565 (which is merged into 0.10 branch and will be in rc2)

12. laanwj closed this on Dec 30, 2014

    ---

13. MarcoFalke locked this on Sep 8, 2021

Milestone
0.10.0