Puzzle 1553 crashes repeatedly

Case number:845829-2005535
Topic:Crash/Hang
Opened by:LociOiling
Status:Open
Type:Bug
Opened on:Thursday, July 26, 2018 - 04:21
Last modified:Tuesday, July 31, 2018 - 03:15

On Windows, several crashes similar to the unhandled exception below. No debug.txt was generated.

The crashes all occurred on high wiggle power.

UNHANDLED EXCEPTION
  1: RaiseException +98 bytes (no line)
  2: _CxxThrowException +101 bytes (no line)
  3: __scrt_throw_std_bad_alloc +28 bytes (no line)
  4: operator new +36 bytes (no line)
  5: ObjexxFCL::FArray2D::FArray2D +93 bytes (no line)
  6: core::optimization::Minimizer::dfpmin_armijo +266 bytes (no line)
  7: core::optimization::Minimizer::run +1306 bytes (no line)
  8: core::optimization::AtomTreeMinimizer::run +886 bytes (no line)
  9: core::optimization::AtomTreeMinimizer::run +31 bytes (no line)
 10: interactive::application::actions::cart::PoseLoopThreadActionCart::run_minimizer_on_work_pose +1006 bytes (no line)
 11: interactive::application::actions::cart::ActionCartGlobalWiggle::thread_body_loop_unlocked +162 bytes (no line)
 12: interactive::application::actions::cart::PoseLoopThreadActionCart::on_thread_run +4684 bytes (no line)
 13: boost::function0::operator() +120 bytes (no line)
 14: interactive::util::Thread::thread_entry_func +69 bytes (no line)
 15: interactive::util::Thread::win32_thread_startup_helper +11 bytes (no line)
 16: BaseThreadInitThunk +36 bytes (no line)
 17: RtlValidSecurityDescriptor +282 bytes (no line)
 18: RtlValidSecurityDescriptor +234 bytes (no line)
(Thu, 07/26/2018 - 04:21  |  10 comments)


LociOiling's picture
User offline. Last seen 4 hours 56 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

Complete log.txt attached.

LociOiling's picture
User offline. Last seen 4 hours 56 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

Here's another one.

rmoretti's picture
User offline. Last seen 1 week 5 days ago. Offline
Joined: 01/15/2010
Groups: None

The "bad_alloc" indicates this is likely due to a memory issue.

Assuming it's not flaky memory on your machine, I'm wondering if it's due to a memory leak that's consuming all the available memory. Do you happen to know how much memory Foldit is taking up when it crashes?

LociOiling's picture
User offline. Last seen 4 hours 56 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

Based on #veteran, others are seeing the same issue. Pretty sure it's not flaky memory.

A crashy solution "feedback 2005535 test" shared with scientists.

Using move test 1.0 on high wiggle power, I was able to get a couple of crashes, at either wiggle or local wiggle functions. Unfortunately, you have to click through 100+ other functions to reach them.

The shared solution crashes pretty quickly using one version of a banded worm recipe, but Bruno's Banded Worm Pairs Inf Filt 1.4.3 doesn't seem to have the same problem. I'll compare the two recipes to see where the differences are.

LociOiling's picture
User offline. Last seen 4 hours 56 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

OK, Banded Worm Pairs Inf Filt 1.4.3 crashed shortly after I finished the previous comment. So that would be a good test with the shared solution. Less clicking than move test 1.0.

I'll still look into recipe differences, since Bruno's Banded Worm seems to run a bit longer than my version.

Also, I forgot to mention, that using Process Explorer on Windows, I see private bytes start at about 670 MB on an idle client. Private bytes seems to peak at about 1.1 GB at the time of the crash. While this is a little high, other Foldit clients have similar values and keep on running.

Watching the memory tab of the System Information window in Process Explorer, there's no sign of any memory shortage leading up to the crash. Commit charge stays under 50%, and available physical memory is over 1.2 GB.

Windows 10 Pro, Intel Core i7 620M (4 logical processors), 8 GB.

LociOiling's picture
User offline. Last seen 4 hours 56 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

Changing the undo graph properties to minimum values seems to resolve the crashing problem.

I used max graph length 25 and memory usage 0%, and made sure to click "Apply" for both settings.

The client has been running for several hours now, where previously it crashed in just minutes.

Thanks to frood66 for the suggestion.

Now we can ponder the meaning of the 0% memory usage. It's really unclear what the difference between 0% and 100% memory usage is when it comes to the undo graph.

alcor29's picture
User offline. Last seen 3 hours 42 min ago. Offline
Joined: 11/16/2012

Hi Loci, Frood. Thanks for the reminder regarding memory settings. I am now testing graph length 100 and memory 0%. No crashing now. Main. Win 10/64 6GB quad core (logical).

LociOiling's picture
User offline. Last seen 4 hours 56 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

*mostly* resolve....

bertro's picture
User offline. Last seen 1 hour 30 min ago. Offline
Joined: 05/02/2011
Groups: Beta Folders

Same crash as Loci:

UNHANDLED EXCEPTION
1: RaiseException +98 bytes (no line)
2: _CxxThrowException +101 bytes (no line)
3: __scrt_throw_std_bad_alloc +28 bytes (no line)
4: operator new +36 bytes (no line)
5: ObjexxFCL::FArray2D::FArray2D +93 bytes (no line)
6: core::optimization::Minimizer::dfpmin_armijo +266 bytes (no line)
7: core::optimization::Minimizer::run +1306 bytes (no line)
8: core::optimization::AtomTreeMinimizer::run +886 bytes (no line)
9: core::optimization::AtomTreeMinimizer::run +31 bytes (no line)
10: interactive::application::actions::cart::PoseLoopThreadActionCart::run_minimizer_on_work_pose +1006 bytes (no line)
11: interactive::application::actions::cart::ActionCartGlobalWiggle::thread_body_loop_unlocked +162 bytes (no line)
12: interactive::application::actions::cart::PoseLoopThreadActionCart::on_thread_run +4590 bytes (no line)
13: boost::function0::operator() +120 bytes (no line)
14: interactive::util::Thread::thread_entry_func +69 bytes (no line)
15: interactive::util::Thread::win32_thread_startup_helper +11 bytes (no line)
16: BaseThreadInitThunk +36 bytes (no line)
17: RtlValidSecurityDescriptor +282 bytes (no line)
18: RtlValidSecurityDescriptor +234 bytes (no line)

georg137's picture
User offline. Last seen 8 hours 35 min ago. Offline
Joined: 08/07/2010
Groups: Contenders

Also same crash as Loci and Bertro while running 'cut and wiggle forever' at high wiggle power. The Foldit client screen simply disappears. But Frood's workaround - setting undo parameters to minimum - is working. Thanks.

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