No dice on tewinget's branch. I do see a lmdb out of space error in addition to the uncaught exception but there is well over 11gb of free space, not factoring in the 3.4gb blockchain.bin that monero already takes up.
Ok I'm going to need more info -
1. What Windows version, and 32-bit or 64-bit?
2. What is the LMDB error, is it something like "MDB_MAP_FULL Environment mapsize limit reached" ?
1. 64-bit
2. This is all I have for the log, nothing as it relates to the limit you described:
2015-Apr-09 18:59:09.839062 Initializing cryptonote protocol...
2015-Apr-09 18:59:09.840062 Cryptonote protocol initialized OK
2015-Apr-09 18:59:09.840062 Initializing p2p server...
2015-Apr-09 18:59:26.854035 Binding on 0.0.0.0:18080
2015-Apr-09 18:59:26.854035 Net service bound to 0.0.0.0:18080
2015-Apr-09 18:59:26.855035 Attempting to add IGD port mapping.
2015-Apr-09 18:59:27.901095 Added IGD port mapping.
2015-Apr-09 18:59:27.901095 P2p server initialized OK
2015-Apr-09 18:59:27.901095 Initializing core rpc server...
2015-Apr-09 18:59:27.901095 Binding on 127.0.0.1:18081
2015-Apr-09 18:59:27.902095 Core rpc server initialized OK on port: 18081
2015-Apr-09 18:59:27.902095 Initializing core...
2015-Apr-09 18:59:27.903095 Loading blockchain from folder 0x401c9c8 ...
2015-Apr-09 18:59:27.904095 Failed to open lmdb environment: There is not enough space on the disk.
2015-Apr-09 18:59:27.904095 Error opening database: Failed to open lmdb environment: There is not enough space on the disk.
2015-Apr-09 18:59:27.905095 ERROR C:/msys64/home/user/bitmonero-blockchain/src/daemon/daemon.cpp:123 Uncaught exception! Failed to initialize core
2015-Apr-09 18:59:27.905095 Deinitializing rpc server...
2015-Apr-09 18:59:27.905095 Deinitializing p2p...
2015-Apr-09 18:59:27.907095 Deinitializing core...
2015-Apr-09 18:59:27.907095 Mining has been stopped, 0 finished
2015-Apr-09 18:59:27.909095 Failed to deinitialize core...
2015-Apr-09 18:59:27.910095 Mining has been stopped, 0 finished
2015-Apr-09 18:59:27.911095 Deinitializing cryptonote_protocol...
Thanks - that's much clearer:)
Problem: There's a lack of sparse file support on Windows, so Windows tries to reserve a full 16gb section on disk (ie. the entire MMAP)
Immediate Resolution: If you need to or want to continue testing you'll need to make sure you have at least 16gb available.
Permanent Resolution: We're making the MMAP allocation dynamic, so it'll start with a much smaller MMAP and then grow it accordingly.
Time Frame: Not the most complicated change, so we should be able to fix this and merge it into master next week.