The following module will eat all available RAM if executed:

import inspect
import unittest.mock
print(inspect.unwrap(unittest.mock.call))

inspect.unwrap has loop protection against functions that wrap themselves, but unittest.mock.call creates new object on demand.

I see two options to fix it:

1) add recursion depth check to inspect.wrap
2) define __wrapped__ on mock._Call so it won't go into recursion.

This is a dupe of https://bugs.python.org/issue25532

Peter, please include x.y.z version with reports (and upgrade first if possible ;-).  This was apparently fixed in #25532 last year for current versions.  With 3.6.4 and 3.7.0b2 I get
Traceback (most recent call last):
  File "F:\Python\a\tem2.py", line 3, in <module>
    print(inspect.unwrap(unittest.mock.call))
  File "C:\Programs\Python37\lib\inspect.py", line 515, in unwrap
    raise ValueError('wrapper loop when unwrapping {!r}'.format(f))
ValueError: wrapper loop when unwrapping call