DebuggerScope::className() should not assert scope->isValid() because the TypeProfiler logs objects it encounters, and may indirectly call JSObject::calculatedClassName() on those objects later, thereby calling DebuggerScope::className() on an invalidated DebuggerScope. The existing handling in DebuggerScope::className() for an invalidated scope (that returns a null string) is sufficient.
<rdar://problem/20790971>
Created attachment 277634 [details] proposed patch.
Comment on attachment 277634 [details] proposed patch. r=me
Thanks for the review. Landed in r200200: <http://trac.webkit.org/r200200>.
Correction: this bug is not <rdar://problem/20790971>. There was a mis-aggregation.
<rdar://problem/25985293>
<rdar://problem/25985379>