Here are the 2 log files mentioned above:

More logs from the same recipe on the same 2 clients
but more different starting structures & input parameters:

Log.txt files

Thanks for the crash logs!

We're especially interested in specific actions that cause a crash. I know this can be difficult to tell when the crash happens in the middle of a recipe—but if you encounter a crash while using a tool (like the Rama Map, or simply Pulling on the protein), please let us know! Especially if you can reproduce the crash more than once!

Rebuid and ReMix are not working on 1659b in the new DevPrev.

Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 546d537b
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915f98e
Exception Code: e06d7363
Exception Offset: 0000c54f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

From log.txt:
SRVR_THRD getting notifications...
Time: 378985 - Tool on_action_complete called
***** STARTING THREAD ActionGlobalMinimize
RT: 11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-3, 467-1, 467-2, 467-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-1, 475-2, 475-3, 476-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-2, 475-3, 476-1, 476-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
Sending SOPs:

Sending SOPs:

core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-1, 466-2, 466-3, 467-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-2, 466-3, 467-1, 467-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 466-3, 467-1, 467-2, 467-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-1, 475-2, 475-3, 476-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-2, 475-3, 476-1, 476-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 475-3, 476-1, 476-2, 476-3!

UNHANDLED EXCEPTION
1: RaiseException +88 bytes (no line)
2: no symbol (no line)
3: no symbol (no line)
4: no symbol (no line)
5: no symbol (no line)
6: no symbol (no line)
7: no symbol (no line)
8: no symbol (no line)
9: no symbol (no line)
10: no symbol (no line)
11: no symbol (no line)
12: no symbol (no line)
13: no symbol (no line)
14: no symbol (no line)
15: no symbol (no line)
16: BaseThreadInitThunk +18 bytes (no line)
17: RtlInitializeExceptionChain +99 bytes (no line)
18: RtlInitializeExceptionChain +54 bytes (no line)

Latest devprev client (with the announced fixes)
Solution shared as "doferror_BP".

I saw one of these "no symbol (no line)" crashes overnight running a remix recipe on 16b9b. Overall, only a couple of crashes, not the repeated crashes others are reporting. Unfortunately, I restarted the client before saving the log file.

I do see these "no proper DoF" messages in log.txt, even without a crash. They involve the permanent cutpoints in the designable section, at segments 466-467 and 475-476 in my solution.

From previous discussions, I think the "no proper DoF" lines come from Rosetta, so there's probably not a direct fix in Foldit. Maybe something happens that clobbers a little memory for each of these messages, eventually leading to a crash.

Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 546d537b
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915f98e
Exception Code: e06d7363
Exception Offset: 0000c54f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Same location.
during wiggle.

And for your information:
https://support.microsoft.com/en-us/help/185294/prb-exception-code-0xe06d7363-when-calling-win32-seh-apis
"
To properly handle the error, you need to wrap the offending code in a
try...catch block. This allows the developer to identify the actual Visual C++ exception that was thrown.

While debugging an application with Microsoft Visual Studio, you can halt the program immediately when this exception occurs, before any handler code is invoked. This gives you a chance to view the offending statement and fix the exception yourself by modifying the variable contents, thereby avoiding an unwind. To set how the debugger handles this exception, follow these steps:

Start debugging your application.
From the Debug menu, click Exceptions.
Within the Exceptions dialog box, select error 0xE06D7363.
Change the value of Action from Stop if not handled to Stop always.

Status
This behavior is by design.
References
Visual C++ Books Online: Exception Handling; Debugging Exceptions

"

Same here. Crashed when I invoked 'wiggle.' Main UI. Win 10/64

Have crashed for times since then. Seems like a crash for every script.

On seventh crash, got a different log from BP's log above. I only checked my log the first 2 times.Crashed 4 times during script. Once wiggling. Once stopping shake.
And this time I think I was stopping a script.

Main. Win 10/64. original UI.

Entire log:

args passed:
'C:\Foldit\Foldit.exe'
args used:
'C:\Foldit\Foldit.exe'
'-resources'
'cmp-resources-44c07dd2606550e85032ccba6e8f0e3a/resources'
'-database'
'cmp-database-fb137240c5d3860cd3853cc25565f8fc/database'
'-interactive_game'
'novice'
'-boinc_url'
'https://fold.it'
'-interactive:interactive_residue_types'
'-ignore_unrecognized_res'
'-out:level'
'200'
'-out:no_color'
'-load_PDB_components'
'false'
We're loading in the hotkeys
loading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileloading hotkey fileWe loaded in the hotkeys
starting the init thread!..
boinc base url: https://fold.it
checking updates...
binary
local: 'fb6cfb0559fda9925ddd3311893e154a'
remote: 'fb6cfb0559fda9925ddd3311893e154a'
database
local: 'fb137240c5d3860cd3853cc25565f8fc'
remote: 'fb137240c5d3860cd3853cc25565f8fc'
resources
local: '44c07dd2606550e85032ccba6e8f0e3a'
remote: '44c07dd2606550e85032ccba6e8f0e3a'
cleaning up old components:
binary 00000000000000000000000000000000
binary fb6cfb0559fda9925ddd3311893e154a
database fb137240c5d3860cd3853cc25565f8fc
resources 00000000000000000000000000000000
resources 44c07dd2606550e85032ccba6e8f0e3a
REPORTING CRASH: 462374
SoundTheme::load: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01
loading: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01/rotamer_land_00.ogg
loading: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01/rotamer_land_01.ogg
loading: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01/rotamer_land_02.ogg
loading: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01/rotamer_land_03.ogg
loading: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01/rotamer_land_04.ogg
loading: cmp-resources-44c07dd2606550e85032ccba6e8f0e3a\resources\sounds/organic_01/rotamer_land_05.ogg
(@init_machine_log)intro_level_version_ is 0

Regarding jeff101's speculation above: I did not add or alter the chains at all; but crashed so much I have stopped working on it for the moment.

Changed devprev issue to Crash/Hang as it happens both in the main and devprev releases, and this is a bug not just an issue.

Problem signature:
Problem Event Name: APPCRASH
Application Name: Foldit.exe
Application Version: 0.0.0.0
Application Timestamp: 52c4c7ce
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915f8e8
Exception Code: c0000005
Exception Offset: 0002e49b
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

From log.txt, skipping most blabla, which again includes a lot of Dof errors..

UNHANDLED EXCEPTION
1: RtlInitUnicodeString +499 bytes (no line)
2: RtlFreeHeap +126 bytes (no line)
3: HeapFree +20 bytes (no line)
4: _free_base +28 bytes (no line)
5: operator delete +11 bytes (no line)
6: boost::detail::sp_counted_impl_p::`scalar deleting destructor' +26 bytes (no line)
7: boost::detail::sp_counted_base::destroy +10 bytes (no line)
8: std::_Destroy_range1 >,boost::shared_ptr *> +97 bytes (no line)
9: core::scoring::ResPairMinimizationData::~ResPairMinimizationData +81 bytes (no line)
10: core::scoring::MinimizationEdge::~MinimizationEdge +533 bytes (no line)
11: core::scoring::MinimizationEdge::`scalar deleting destructor' +11 bytes (no line)
12: core::scoring::MinimizationGraph::delete_edge +22 bytes (no line)
13: utility::graph::Graph::delete_everything +33 bytes (no line)
14: core::scoring::MinimizationGraph::~MinimizationGraph +56 bytes (no line)
15: core::scoring::MinimizationGraph::`scalar deleting destructor' +11 bytes (no line)
16: boost::detail::sp_counted_impl_p::dispose +13 bytes (no line)
17: core::scoring::Energies::~Energies +407 bytes (no line)
18: core::scoring::Energies::`scalar deleting destructor' +11 bytes (no line)
19: boost::detail::sp_counted_impl_p::dispose +13 bytes (no line)
20: core::pose::Pose::~Pose +507 bytes (no line)
21: core::pose::Pose::`scalar deleting destructor' +11 bytes (no line)
22: boost::detail::sp_counted_impl_p::dispose +13 bytes (no line)
23: interactive::application::actions::cart::PoseLoopThreadActionCart::run_minimizer_on_work_pose +1263 bytes (no line)
24: interactive::application::actions::cart::ActionCartGlobalWiggle::thread_body_loop_unlocked +162 bytes (no line)
25: interactive::application::actions::cart::PoseLoopThreadActionCart::on_thread_run +4809 bytes (no line)
26: boost::function0::operator() +120 bytes (no line)
27: interactive::util::Thread::thread_entry_func +69 bytes (no line)
28: interactive::util::Thread::win32_thread_startup_helper +14 bytes (no line)
29: BaseThreadInitThunk +18 bytes (no line)
30: RtlInitializeExceptionChain +99 bytes (no line)
31: RtlInitializeExceptionChain +54 bytes (no line)
Sending SOPs:

Also for me, this is a non-playable puzzle unfortunately, so I will stop trying this round.

I'm amazed (tho not surprised) that a 499 seg puzzle has even been set.

Years ago it was accepted that anything over 180 segs was 'pushing it'

Ok - so many now have more powerful machines - but many do not. Many with powerful machines cannot play it without issues.

This puzzle is a waste of computer time to most (it seems)

How about a much smaller version - just to get ideas....work from there. Maybe something useful will be found - something to work on.

Right now it simply crashes too often - and very few will even play it through.

Just a thought FC - but ignore the issue at yr loss in solutions.

I say the above in the best possible taste (of course)

I can verify that even if you do not add or delete segments it still crashes during wiggle.

"One thing perhaps unique to my structure is that
I removed and added several different segments
in a somewhat haphazard order. Maybe folks who
seem immune to the crashes didn't remove or add
any segments, leaving the mutable strand lengths
as given."

It seems to me, after some experimentation, that the MAC client is not affected, so it may be a Windows specific issue.

sorry to disappoint BP - the mac client is certainly affected.

I'm running main version of Linux client. It was relatively stable.
But more interesting for me is memory consumption on this puzzle.
On puzzle load it takes approximately 0,8GB.
After start of Tvdl Enhanced DRW it grow to ~1.9GB.
After subsequent launch of some other scripts it grow to ~ 3GB.