98849882a2
In theory, resetting clearStack's inline call count every time late rejection handling does a setTimeout should reduce the performance penalty in some environments. In practice, it doesn't: * In Chrome and FF, late rejection handling has no measurable penalty. * In Safari, resetting the inline call count actually slows things down considerably(!). * In Node, clearStack doesn't use setTimeout so there is no benefit.