Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Identified a bug with 0.4.9 windows binary, please use 0.4.9-a instead  (Read 502 times)

0 Members and 1 Guest are viewing this topic.

Offline DACSunlimited

  • Full Member
  • ***
  • Posts: 136
    • View Profile

Sorry about that, will update status ASAP.
« Last Edit: August 28, 2014, 05:46:36 PM by DACSunlimited »

Offline Riverhead

The cutting edge cuts deep  :o

Offline JA

  • Hero Member
  • *****
  • Posts: 650
    • View Profile
  • Payrate: 666%
haha lol

just as i saw this post i took a look at my syncing client -- BitsharesX crashed  :D

Offline DACSunlimited

  • Full Member
  • ***
  • Posts: 136
    • View Profile
We got to identify the stuck problem on a block finally, this was supposed to only happen on debug mode.

But unfortunately, the windows version was built without NDEBUG flag, which might be introduced from CMake 3.0.

So users on windows, please download the new BitSharesX-0.4.9-a.exe version.

https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.9/BitSharesX-0.4.9-a.exe

If you were stuck with some block, please re-sync the chain.

Sorry about confusion.

 

Google+