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

Case number:845829-1998858
Topic:Crash/Hang
Opened by:Bletchley Park
Status:Open
Type:Bug
Opened on:Friday, December 5, 2014 - 21:09
Last modified:Wednesday, December 10, 2014 - 16:03

Attached the filed bugreport. as the original triggered the spam filter...

AttachmentSize
foldit bugreport 20141205.txt8.8 KB
(Fri, 12/05/2014 - 21:09  |  15 comments)


Joined: 05/19/2009
Groups: Contenders

New log file is now 8.4 Gigabytes in less than 48 HOURS !!!!

Joined: 05/19/2009
Groups: Contenders
Type: DevPrev Issue » Bug

Upping this to a serious BUG.

spmm's picture
User offline. Last seen 27 weeks 3 days ago. Offline
Joined: 08/05/2010
Groups: Void Crushers

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

Joined: 05/19/2009
Groups: Contenders

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's picture
User offline. Last seen 27 weeks 3 days ago. Offline
Joined: 08/05/2010
Groups: Void Crushers

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

Joined: 05/19/2009
Groups: Contenders

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's picture
User offline. Last seen 27 weeks 3 days ago. Offline
Joined: 08/05/2010
Groups: Void Crushers

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.

Joined: 05/19/2009
Groups: Contenders

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.

Joined: 05/19/2009
Groups: Contenders

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. ***

NickyCGS's picture
User offline. Last seen 4 years 17 weeks ago. Offline
Joined: 06/27/2013
Groups: Repro-men

Thanks for all of the feedback Bletchley, I left some clients running over the weekend to verify this issue. This issue has already been forwarded to the team and should hopefully be resolved soon.

Joined: 05/19/2009
Groups: Contenders

Thank you !

brow42's picture
User offline. Last seen 2 weeks 4 days ago. Offline
Joined: 09/19/2011
Groups: None

I'm pretty sure this giant log file issue has come up before, I but I can't find it. The easiest way to never have a giant log file is to make a small log.txt file read-only.

Joined: 05/19/2009
Groups: Contenders

That is a smart workaround indeed Brow, but then the devs wont know what is wrong with the client. That is the purpose of the log file.

spmm's picture
User offline. Last seen 27 weeks 3 days ago. Offline
Joined: 08/05/2010
Groups: Void Crushers

http://fold.it/portal/node/994683 - giant log file, May 2013 - BP was up to 27GB - excess Rosetta info apparently.

Joined: 09/24/2012
Groups: Go Science

aaah ! now I understand why my log files are so big.

I rarely close Foldit because I've different clients running: the log is then never reinitialized.

Now that my latest client crashed, I see a log of 7.6 Gb (after several weeks folding with 2 clients).

None of my softwares is able to open it.

Sitemap

Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, RosettaCommons