OutOfMemoryException thrown when mock is called many times - Option for verification opt-out needed

[thefellow3j]

I have a situation in which a mock needs to be called over 1,000,000 times, with parameters. Because call capturing is automatic, Moq captures each call and its data and stores it in memory.

In this situation, I have no need for the verification of mock methods being called. Can you implement a constructor parameter or MockRepository option that can explicitly enable or disable mock verification, subsequently avoiding capturing calls and storing their data in memory?

[janslav]

Seconding this, it's a real issue in bigger tests.

[stakx]

Until (if) such an opt-out is implemented, have you tried (as a workaround only, of course) resetting the mock using mock.ResetCalls() e.g. after every few thousand calls?

[stakx]

Now that we have Mock.Switches and MockRepository.Switches (feature / compatibility switches), this probably wouldn't be too difficult to implement.

@thefellow3j, @janslav - since this issue has been at sleep for a while... is automatic call capture by default still a problem for you, or can we close this?

[stakx]

If you're still interested in this, please post back. Until then, I am closing this issue due to inactivity.

[AqlaSolutions]

I need this