We have several actions that are chained one after another in this manner:

1. Action is dispatched
2. A StoreSubscriber receivesnewState callback on state change
3. It dispatches another Action on the same Store
4. Another StoreSubscriber (or maybe the same one) receivesnewState callback on state change
5. It dispatches another Action on the same Store

These chains are not infinitely recursive, their depth is 2-4 actions. They all operate on single (main) thread synchronously. We see a crash when 2nd or 3rddispatch is called inside ReSwift. It occurs with different action sequences. One case we can reproduce 100% in debug configuration (-Onone), but it's not reproduced in release configuration.

Stacktrace top is__swift_instantiateConcreteTypeFromMangledName