workaround is functional, just a little frustrating without auto-save between scenarios especially if it glitches on one of the last scenarios to complete since each scenario takes a fair amount of time

Scenario is actually 5th from the left*
Saving - exiting - resuming scenario also seems to have no positive effect

(gdb) bt full
#0 0x0a02b515 in ?? ()
No symbol table info available.
#1 0xf75250ee in clone () from /lib/libc.so.6
No symbol table info available.
(gdb) info registers
eax 0xffffffff -1
ecx 0xf6f6a790 -151607408
edx 0xa02b4d8 167949528
ebx 0x0 0
esp 0xf69fd2ec 0xf69fd2ec
ebp 0xf69fd428 0xf69fd428
esi 0xf6f6a79c -151607396
edi 0x0 0
eip 0xa02b515 0xa02b515
eflags 0x210296 [ PF AF SF IF RF ID ]
cs 0x23 35
ss 0x2b 43
ds 0x2b 43
es 0x2b 43
fs 0x0 0
gs 0x63 99

Not sure if I'd call this resolved, it appears to still be happening on all centos boxes:

We've now seen 3 different certified instances of this fault manifesting on different physical systems, virtual systems and operating systems - all 32 bit Linux.