vikky2904:

Do you think it might be because it encountered a nan or inf value in flow? Thoughts?


This might be the case, but I’m also unable to reproduce it using NaNs for x and flow.
A NaN value should not cause an illegal memory access, but should rather yield a proper error message, so please let us know, if you are able to reproduce this behavior and we should fix it.