as initially reported in rspec/rspec-rails#2049

The issue occurs when a class defines an `inspect` method which depends on
methods that have been stubbed to e.g. `receive(...).at_most(n).times`.
Failures try to call `inspect` which fails which calls `inspect` which ...

The error generator may make subsequent calls back in to the erroring
method. This prevents those calls from cascading errors or incrementing
the call count.

following comments from CR

If the error generator sends a message that we've expected `exactly` or `at_most` some number of times, we get a recursive error and stack overflow. This ensures that if we re-`invoke` while already `invoke`ing, we don't increment the count or allow errors to bubble up.