Some recent pypy update started to cause segfaults when aborting too long traces when the trace limit is very high. Setting it lower by default helps, and at least doesn't seem to have an adverse effect on UI responsiveness. I haven't run benchmarks, however, so we should see what codespeed says.
The other refactoring in there is to speed up simulation when the code is not jitted, which also (hopefully) makes it a little clearer.
Some recent pypy update started to cause segfaults when aborting too long traces when the trace limit is very high. Setting it lower by default helps, and at least doesn't seem to have an adverse effect on UI responsiveness. I haven't run benchmarks, however, so we should see what codespeed says.
The other refactoring in there is to speed up simulation when the code is not jitted, which also (hopefully) makes it a little clearer.