6.7 Gigabyte log file with "core.scoring.CartesianBondedEnergy"

Started by Bletchley Park

spmm Lv 1

Weird - on Mac 10.10.1 it is 1.8MB and I have been running for days with several crashes : Applications> foldit.app > content > resources >log.txt

Bletchley Park Lv 1

Since posting this 6 hours ago, it grew by one more gigabyte. That is consistent with the size groth since start, so the fill-rate is 1 gigabyte per 6 hours.

spmm Lv 1

I was curious so, on a standard Dell (Win 7) Game build ID: 20141110-b740d73796-win_x86

I have been running a rebuilder on one client with the ED puzzle from noon - 5.30pm 13kb > 8,200kb in that time.

Rather a lot of this in the log file:

core.scoring.CartesianBondedEnergy: Creating new peptide-bonded energy container (153)
core.optimization.LineMinimizer: Inaccurate G! step= 1.52588e-007 Deriv= -47.6681 Finite Diff= 70.8147
core.optimization.LineMinimizer: Inaccurate G! step= 3.8147e-008 Deriv= -47.6681 Finite Diff= 70.8153

It is Very Unhappy with container 153. Not gigabytes but that perhaps depends on how many clients you have running.
cheers

Bletchley Park Lv 1

That is exactly what I find spmm, but in my case a huge number of lines with the container (153) message.

WORKAROUND:
I have come up with a workable temporary fix if you run Windows;

exit all clients
open the windows file explorer
locate the log.txt file (usually in program files x86\foldit\log.txt)
right-click on the existing file,
select properties
select 'advanced'
checkmark 'compress contents to save disk space'
click 'apply'
click 'ok'

The file will still be huge, but will take up only a fraction on disk, this will buy you time until the devs can come up with a fix (hopefully today). It is also wise to regularly stop all clients and copy a small file to 'log.txt', it will be overwritten by the new clients but keep the 'compressed' attribute.

Cheers

spmm Lv 1

Up to 8.8mb on the mac now since this morning's crash, one client running ED: Build ID: 20141112-b740d73796-osx_x86-devprev. Workaround looks like a good idea. Is anything reading it?, otherwise it is just hogging disk space.

Bletchley Park Lv 1

It is produced by the clients, and serves as a log for the devs in case of trouble. I would think they have a debug message that is not switched off somewhere in new code. Nothing else is reading it, but you cannot delete the file while at least one client is still running.

Bletchley Park Lv 1

I found more redundant debug info, after running just 45 minutes of one client, I had a 100 megabyte log filled with stuff like:

protocols.flxbb.LayerDesignOperation: Active layers: surface
protocols.flxbb.LayerDesignOperation: —————————————
protocols.flxbb.LayerDesignOperation: 61 done
protocols.flxbb.LayerDesignOperation: Residue 62
protocols.flxbb.LayerDesignOperation: ss=H Neighbors= 5.54
protocols.flxbb.LayerDesignOperation: basic layer = core
protocols.flxbb.LayerDesignOperation: Active layers: core
protocols.flxbb.LayerDesignOperation: —————————————
protocols.flxbb.LayerDesignOperation: 62 done
protocols.flxbb.LayerDesignOperation: Residue 63
protocols.flxbb.LayerDesignOperation: ss=H Neighbors= 0.84
protocols.flxbb.LayerDesignOperation: basic layer = surface
protocols.flxbb.LayerDesignOperation: Active layers: surface
protocols.flxbb.LayerDesignOperation: ————————————-

** Please get rid of this debug info asap, thanks. **