Closed jansvoboda11 closed 7 years ago
Sure, the mock records every call. Hence the memory is expected to increase in such a loop.
On Dec 28, 2016 1:33 PM, "Jan Svoboda" notifications@github.com wrote:
Closed #76 https://github.com/eranpeer/FakeIt/issues/76.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/eranpeer/FakeIt/issues/76#event-906449452, or mute the thread https://github.com/notifications/unsubscribe-auth/ACc8gky4YpieEZ8pNTKwuk0jf8KzzgcGks5rMkj2gaJpZM4LWpAA .
Yeah, I've realised that the next day, thanks for the reply.
Hello. I've noticed a lot of memory being allocated when using AlwaysDo in my tests. Memory usage steadily increases when a mock is used in long-running loop. You should be able to reproduce it by running the code below.
Is this a bug in the library, or am I doing something wrong? Thanks for your answer.