Alright, I've nailed down the exact cause of the issue and we should hopefully have a fix out soon. In the meantime, in your options.txt file change "graph_options/graph_length_value" : "100" to "graph_options/graph_length_value" : "25" or another lower number. Unfortunately it appears that the Undo Graph size is the cause of both these crashes and the memory usage detailed in http://fold.it/portal/node/997741
Added by Timo: Be aware that if you have multiple clients running you should change the graph setting on all clients before closing that client.
You can also edit this in game by decreasing Max Graph Length in the Graph Properties option of the Undo menu.
should everyone using devprev restrict graph length until there is a fix?
I second that, thanks Nicky. I haven't had a crash on 897 since changing the option.
A pic may also be of use Win 8.1:
See memory column:
897: 4 - 1,268.0 MB forgot to reduce the graph length, running a fuser with cuts, almost double the memory but should not crash the machine, as you can see it is only using 16% total and that is steady.
897: 3 - 748.8 MB - Void Crusher - graph memory and length reduced to 25
897: 2 - 888.8 MB -DRW - graph memory and length reduced to 25
Was previously crashing after an hour or so of DRW.
'should not crash the machine' - should be 'should not crash the client' as there appears to be only 16% use of RAM.
It appears that graph properties apply to ALL PUZLs - so if you need to set it low ie 25 for a big one 200+ residues, then it is 25 for the 71 residues puzls as well.
imo we need more practice on these big ones :) to work in conjunction with the smaller ones. Given the idea that we can step back through Undo.
Is there any word on when this will be fixed by an update?
I'm having difficulties recovering progress made on un-evolved Evos that have open cut-point scores higher than the credit-best scores. Clicking "restore credit best" restores the cut-point value and not the highest score without cut-points. In the past, it wasn't difficult to find a credit-best score in the undo buffer, but at 25, it is often impossible.
We are working hard on getting this resolved, but it's proved trickier than we had hoped.
We hope to have the fix for this quite soon and post it to devprev.
Thank you for your patience with this nasty one!
