Troubles reproducing timeout issue outside of oss-fuzz

We have a recent report ( https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=54307 ) that is identified as a timeout within oss-fuzz. This is reproducible using the provided testcase using the instructions here: https://google.github.io/oss-fuzz/advanced-topics/reproducing/#reproducing-bugs

During the test I inspected what payload was being provided to the fuzz test here: https://github.com/gravitational/teleport/blob/master/lib/services/fuzz_test.go#L35

When the same payload is provided as a `f.Add` and then run outside of oss-fuzz I am not not able to reproduce the timeout condition. I suspect there may be something `oss-fuzz` specific in play, possibly a bug.

I have attached a (very large) `f.Add` code line that can be added to the test file linked above for you to be able to test:
[1671216715360-f0c5341e.txt](https://github.com/google/oss-fuzz/files/10248557/1671216715360-f0c5341e.txt)

Let me know if you have any ideas why a timeout in oss-fuzz is reproducible but when run within go's test framework execution completes in under 1 second. Also let me know if I can provide any additional context to help. Thank you!