[SOLVED] 0.4.23 (0.4.22) Problems with indexing (win7 32bit)

Started by tonyk, October 29, 2014, 07:51:51 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

zerosum

#5
The magic of (re)indexing in 0.4.23.1  :)





===================================================================================


And this is the way, I like them bitAssets. Truly good news  :)




vikram

Quote from: tonyk on October 29, 2014, 07:59:49 PM
Quote from: xeroc on October 29, 2014, 07:56:56 PM
From what I read from a post from "dannotestein" (wow .. three times "from" :) )
the build process for the windows client screw something up and they are currently recompiling the windows client ...

Thanks.
It will be under the same version 0.4.23, right?

Yes, but it may or may not fix this issue--there is a memory issue on 32 bit windows we are looking into: https://github.com/BitShares/bitshares_toolkit/issues/759

tonyk

Quote from: xeroc on October 29, 2014, 07:56:56 PM
From what I read from a post from "dannotestein" (wow .. three times "from" :) )
the build process for the windows client screw something up and they are currently recompiling the windows client ...

Thanks.
It will be under the same version 0.4.23, right?
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

xeroc

From what I read from a post from "dannotestein" (wow .. three times "from" :) )
the build process for the windows client screw something up and they are currently recompiling the windows client ...

tonyk

Nothing else running on win 7/ 32 bit. Installing the new version 0.4.32 (same happened with 0.4.22, but I do not have pics for that)

At about 2 G memory taken, the client crushes... During indexing the program is taking 25% of the CPU resources. (in my mind it is just one thread running, one a 4 virtual core (2 physical one CPU).





Trying to restart the client.






Restarted the computer, copied the database as some of the client restarts managed to kill it. ( I do not remember which)





Lack of arbitrage is the problem, isn't it. And this 'should' solves it.