1514 crashed a fifth time with UI not minimized.

Case number:845829-2005121
Topic:Crash/Hang
Opened by:alcor29
Status:Open
Type:Bug
Opened on:Tuesday, May 1, 2018 - 17:53
Last modified:Tuesday, May 8, 2018 - 17:03

Crashed when trying to type in chat box with script running.

SRVR_THRD getting notifications...
Sending SOPs:

Sending SOPs:

Sending SOPs:

SRVR_THRD getting notifications...
Sending SOPs:

Sending SOPs:

Sending SOPs:

delta_score: 1020.49
Playing sound: 8
***** ENDING THREAD ActionGlobalMinimize
Tool on_action_complete called
***** STARTING THREAD ActionGlobalMinimize
SRVR_THRD getting notifications...

UNHANDLED EXCEPTION
1: RaiseException +98 bytes (no line)
2: alIsAuxiliaryEffectSlot +603490 bytes (no line)
3: alIsAuxiliaryEffectSlot +488837 bytes (no line)
4: alIsAuxiliaryEffectSlot +481468 bytes (no line)
5: library_main +7655517 bytes (no line)
6: library_main +34548826 bytes (no line)
7: library_main +34560090 bytes (no line)
8: library_main +31625622 bytes (no line)
9: library_main +31624719 bytes (no line)
10: library_main +5912680 bytes (no line)
11: library_main +5488976 bytes (no line)
12: library_main +5909420 bytes (no line)
13: library_main +370360 bytes (no line)
14: library_main +3409717 bytes (no line)
15: library_main +3410155 bytes (no line)
16: BaseThreadInitThunk +36 bytes (no line)
17: RtlGetAppContainerNamedObjectPath +311 bytes (no line)
18: RtlGetAppContainerNamedObjectPath +263 bytes (no line)
Sending SOPs:

(Tue, 05/01/2018 - 17:53  |  23 comments)


carsonfb's picture
User offline. Last seen 3 weeks 5 days ago. Offline
Joined: 09/23/2012
Groups: None

Crashing details

I am running Windows 10 Pro 64-bit and the puzzle crashes on me frequently when I "wiggle sidechains" or run any script that utilizes that feature.

I have 16GB of RAM with ~20% free when it crashes, so I don't believe memory is an issue. Also, I only run one client at a time.

alcor29's picture
User offline. Last seen 16 hours 23 min ago. Offline
Joined: 11/16/2012
Topic: General » Crash/Hang
Type: Suggestion » Bug

Crashed again. Strange errors in log.

core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 190-1, 190-2, 190-3, 191-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 190-2, 190-3, 191-1, 191-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 190-3, 191-1, 191-2, 191-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 200-1, 200-2, 200-3, 201-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 200-2, 200-3, 201-1, 201-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 200-3, 201-1, 201-2, 201-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 210-1, 210-2, 210-3, 211-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 210-2, 210-3, 211-1, 211-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 210-3, 211-1, 211-2, 211-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 220-1, 220-2, 220-3, 221-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 220-2, 220-3, 221-1, 221-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 220-3, 221-1, 221-2, 221-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 230-1, 230-2, 230-3, 231-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 230-2, 230-3, 231-1, 231-2!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 230-3, 231-1, 231-2, 231-3!

UNHANDLED EXCEPTION
1: RaiseException +98 bytes (no line)
2: alIsAuxiliaryEffectSlot +603490 bytes (no line)
3: alIsAuxiliaryEffectSlot +488837 bytes (no line)
4: alIsAuxiliaryEffectSlot +481468 bytes (no line)
5: library_main +7655517 bytes (no line)
6: library_main +34548826 bytes (no line)
7: library_main +34560090 bytes (no line)
8: library_main +31625622 bytes (no line)
9: library_main +31624719 bytes (no line)
10: library_main +5912680 bytes (no line)
11: library_main +5488976 bytes (no line)
12: library_main +5909420 bytes (no line)
13: library_main +370360 bytes (no line)
14: library_main +3409717 bytes (no line)
15: library_main +3410155 bytes (no line)
16: BaseThreadInitThunk +36 bytes (no line)
17: RtlGetAppContainerNamedObjectPath +311 bytes (no line)
18: RtlGetAppContainerNamedObjectPath +263 bytes (no line)
Sending SOPs:

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

Just clicked on Cut and Wiggle Forever script and crashed above.

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

If I run Cut and wiggle on medium it doesn't crash; on high, it does.

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

I wonder if this doesn't have something to do with jflat comments on https://fold.it/portal/node/2005040.
the problem may be with cuts? But I'm on main. I thought the prob was in devprev.

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

I wonder if this doesn't have something to do with jflat comments on https://fold.it/portal/node/2005040.
the problem may be with cuts? But I'm on main. I thought the prob was in devprev.

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

Seeing similar problems on devprev, Windows 10 Home.

The crashes happen while working on a teammate's share on high wiggle power. So far, no crashes on solo at low wiggle power.

Lots of "no proper DoF can be found for these four atoms" errors in the log.

No debug.txt, the following exception in log.txt:

UNHANDLED EXCEPTION
  1: RaiseException +98 bytes (no line)
  2: alIsAuxiliaryEffectSlot +694274 bytes (no line)
  3: alIsAuxiliaryEffectSlot +579621 bytes (no line)
  4: alIsAuxiliaryEffectSlot +572254 bytes (no line)
  5: library_main +7690141 bytes (no line)
  6: library_main +34551642 bytes (no line)
  7: library_main +34562906 bytes (no line)
  8: library_main +31628550 bytes (no line)
  9: library_main +31627647 bytes (no line)
 10: library_main +5949342 bytes (no line)
 11: library_main +5496834 bytes (no line)
 12: library_main +5944748 bytes (no line)
 13: library_main +371112 bytes (no line)
 14: library_main +3400005 bytes (no line)
 15: library_main +3400443 bytes (no line)
 16: BaseThreadInitThunk +36 bytes (no line)
 17: RtlGetAppContainerNamedObjectPath +311 bytes (no line)
 18: RtlGetAppContainerNamedObjectPath +263 bytes (no line)
LociOiling's picture
User offline. Last seen 2 hours 54 min ago. Offline
Joined: 12/27/2012
Groups: Beta Folders

Easy procedure to recreate:

1. Reset puzzle
2. Set wiggle power to high
3. Run a Cut & Wiggle recipe.

Cut and Wiggle 1.5 worked as a Cut & Wiggle recipe, using default settings.

bkoep's picture
User offline. Last seen 2 hours 50 min ago. Offline
Joined: 11/15/2012
Groups: None

Thanks! Steps to reproduce are immensely helpful for tracking bugs, especially when there is so little info in the log files!

Susume's picture
User offline. Last seen 4 days 16 hours ago. Offline
Joined: 10/02/2011

Just to be contrary, I am not getting a crash on 1514 on Win 10 devprev. I have tried both Cut And Wiggle Forever and Cut and Wiggle 1.5, on high, from a reset puzzle, and have not gotten any crashes. I do see *lots* of "[ ERROR ] No proper DoF can be found for these four atoms:" in the log.txt, but it just keep chugging along anyway.

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

Is it possible that resetting may change something which enables cut to be handled?

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

On the other hand Loci reset before testing and he still crashed. https://fold.it/portal/node/2005121

jausmh's picture
User offline. Last seen 1 day 11 hours ago. Offline
Joined: 05/19/2017
Groups: Marvin's bunch

I did run C&W on High (Win10Home-Client) tried to open the log-Window and the client froze and died:

The tail of the log-file is:

***** ENDING THREAD ActionGlobalMinimizeBackbone
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
***** STARTING THREAD ActionRepack
delta_score: 159.822
Playing sound: 5
***** ENDING THREAD ActionRepack
Tool on_action_complete called
***** STARTING THREAD ActionGlobalMinimizeSidechains
delta_score: 59.2724
Playing sound: 5
***** ENDING THREAD ActionGlobalMinimizeSidechains
Tool on_action_complete called
***** STARTING THREAD ActionGlobalMinimizeBackbone
delta_score: 139.35
Playing sound: 5
***** ENDING THREAD ActionGlobalMinimizeBackbone
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
Tool on_action_complete called
***** STARTING THREAD ActionRepack
Sending SOPs:

delta_score: -42.3701
Playing sound: 3
***** ENDING THREAD ActionRepack
Tool on_action_complete called
***** STARTING THREAD ActionGlobalMinimize

UNHANDLED EXCEPTION
1: RaiseException +98 bytes (no line)
2: alIsAuxiliaryEffectSlot +603490 bytes (no line)
3: alIsAuxiliaryEffectSlot +488837 bytes (no line)
4: alIsAuxiliaryEffectSlot +481468 bytes (no line)
5: library_main +7655517 bytes (no line)
6: library_main +34548826 bytes (no line)
7: library_main +34560090 bytes (no line)
8: library_main +31625622 bytes (no line)
9: library_main +31624719 bytes (no line)
10: library_main +5912680 bytes (no line)
11: library_main +5488976 bytes (no line)
12: library_main +5909420 bytes (no line)
13: library_main +370360 bytes (no line)
14: library_main +3409717 bytes (no line)
15: library_main +3410155 bytes (no line)
16: BaseThreadInitThunk +36 bytes (no line)
17: RtlGetAppContainerNamedObjectPath +311 bytes (no line)
18: RtlGetAppContainerNamedObjectPath +263 bytes (no line)

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

Running CW today. Went smoothly. Gained 100 points and then crashed with IRC error 5 again. Couldn't see what n= was equal to when it crashed. Or was it some random IRC fluctuation. Did not touch program, nor did I touch chat.

core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 231-3, 232-1, 232-2, 232-3!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 238-1, 238-2, 238-3, 239-1!
core.kinematics.AtomTree: [ ERROR ] No proper DoF can be found for these four atoms: 238-2, 238-3, 239-1, 239-2!

UNHANDLED EXCEPTION
1: RaiseException +98 bytes (no line)
2: alIsAuxiliaryEffectSlot +603490 bytes (no line)
3: alIsAuxiliaryEffectSlot +488837 bytes (no line)
4: alIsAuxiliaryEffectSlot +481468 bytes (no line)
5: library_main +7655517 bytes (no line)
6: library_main +34548826 bytes (no line)
7: library_main +34560090 bytes (no line)
8: library_main +31625622 bytes (no line)
9: library_main +31624719 bytes (no line)
10: library_main +5912680 bytes (no line)
11: library_main +5488976 bytes (no line)
12: library_main +5909420 bytes (no line)
13: library_main +370360 bytes (no line)
14: library_main +3409717 bytes (no line)
15: library_main +3410155 bytes (no line)
16: BaseThreadInitThunk +36 bytes (no line)
17: RtlGetAppContainerNamedObjectPath +311 bytes (no line)
18: RtlGetAppContainerNamedObjectPath +263 bytes (no line)
IRC::run error, code = 5, desc = Remote connection closed
Exiting IRC::run

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

Just as a recap, puzzle 1514 tends to crash on high wiggle power.

I've been trying various things, here are a few observations.

First, a few things we can cross off.

I don't think the IRC error 5 has anything to do with the crash, seems more likely it's just part of the client shutting down after an error.

Similarly, the DoF error messages are mostly harmless. They don't always appear, and you can crash even if they don't appear.

The only lines in log.txt that seem to matter are the unhandled exeception and the numbered lines that follow. The good part is that we seem to getting the exact same exception, which isn't always the case.

Next, there are some exceptions to the crashing. An older "V1" LWS recipe is running where newer "V2" Banded Worm recipes fail. And Susume didn't crash when she tried my procedure (see above).

I suspect the difference may have something to do with undo. Recipes which were adapted for sketchbook may be less crashy than similar recipes. The strategy of doing a quicksave, trying something, and doing a quickload if there's no gain, may help. Avoiding recentbest may also be beneficial.

(On the other hand, just doing a "w" wiggle can cause a crash in some cases, so these workarounds are not going to be 100%.)

On the setting side, adjusting the size of the undo graph and memory usage might be worthwhile. These settings are found under "Graph Properties" on the the Undo menu.

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

So far, setting memory usage to 0% in Undo -> Graph Properties seems to have eliminated the quick crashes on 1514 with high wiggle power.

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

I also have Max Graph Length set to 25 in Undo -> Graph Properties. That setting by itself didn't prevent the crashes. Perhaps the combination of Max Graph Length and Memory Usage is the ticket.

Setting Memory Usage to a higher percentage may also work. Previous feedback indicated 80% was a good value, but I haven't tried it on 1514. Zero percent is working well for me.

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

On my old 32-bit laptop, changing the Graph Properties does not prevent crashing on high wiggle power. This laptop is running an up-to-date version of Windows 10 Pro.

On my 64-bit systems (Win 10 Pro and Home), setting Memory Usage to 0% and Max Graph Length to 25 still seems to be the magic ticket to fixing 1514.

Hanto's picture
User offline. Last seen 10 hours 11 min ago. Offline
Joined: 05/10/2008
Groups: None

50% Graph Mem allocation does NOT work, that was my original settings. Working with your 0% settings now and all 8 clients are presently working. All computers using Crucial 1600L DDR3 16 GB except my 2 oldest desktops. BS ( band strength ) is NOT primary cause of this crash or dying clients. Devs, we need much better error handling on the clients, a truely good reason for a more complex client.

Hanto's picture
User offline. Last seen 10 hours 11 min ago. Offline
Joined: 05/10/2008
Groups: None

Sorry Loci, downvoted your comments because I can't see the icon properly

bkoep's picture
User offline. Last seen 2 hours 50 min ago. Offline
Joined: 11/15/2012
Groups: None

Thanks all for this excellent feedback! Unfortunately, we're still having a tough time reproducing this crash on our end, but your feedback has given us some ideas!

It's most strange that these issues are cropping up in this particular puzzle, while there were no problems in other Revisited puzzles with a similar setup. When Puzzle 1514 expires tomorrow it will be replaced by Puzzle 1517, also with a similar setup.

Please let us know if this bug persists in the new Puzzle 1517! That will help us figure out if the problem is peculiar to this puzzle for some reason, or if it is general to Revisited puzzles.

Hanto's picture
User offline. Last seen 10 hours 11 min ago. Offline
Joined: 05/10/2008
Groups: None

7 0f 8 clients survived single recipe testing using 0% Mem allocation on Graph. I had tried 25% earlier but client kills approached 50% so changed them to 0%. No modified BS ( band strength ) during this testing. Upon reload of failed client, found mem allocation again at 50% meaning APPLY is not doing very good job of accepting and maintaining desired settings. Only one way to be sure settings have been accepted is simply shut down client where settings have adjusted, reload and verify settings are desired. Reasonably good chance that the client would have survived if the APPLY worked. Ive seen this on several clients and platforms now. Win 10 x64 RS4

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

Thanks bkoep. Had no problems with 1517.

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