Bug: Invoking a mock too many times leads to halting execution

Expected Behavior

Invoking a mockk should never cause a test to hang. If too many invocations lead to performance issues, it would be better to either:

• throw an exception once a reasonable cap is reached
• rotate away old data

Current Behavior

After invoking a mock around 130 000 times (on my machine, running JDK 15 on Windows) further invocations will hit a wall and take forever (minutes) to finish.

Steps to Reproduce

I made a small reproduction repo here: https://github.com/Kantis/mockk-repro

1. Run ./gradlew test -i and you’ll see some output as the mock is invoked over and over until it causes problems.

Context

• MockK version: 1.11.0
• OS: Windows
• Kotlin version: 1.5.10 (Also applies to 1.4.32)
• JDK version: 15
• ~JUnit version~ Kotest: 4.6.0
• Type of test: Unit test

[Raibaz]

This shouldn’t be too hard to fix, it should be just a matter of setting a cap to the size of recorded calls and throwing a clear enough exception when the size exceeds a threshold.

(It should be a very rare case though)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If you are sure that this issue is important and should not be marked as stale just ask to put an important label.