Perhaps it is possible to increase the limit (I suspect this was a check for infinite loops, thinking this was a high enough value) and disable this assertion in release builds.
Perhaps it is possible to increase the limit (I suspect this was a check for infinite loops, thinking this was a high enough value) and disable this assertion in release builds.