When converting stack traces between Firefox and Chrome that include eval frames, at least one frame is guaranteed to contain undefined as its frame type, name, or something else.
As a temporary workaround, these faulty frames are being removed entirely during conversion.
But, this isn't ideal. The goal in future versions is to make the conversion more seamless, contribution is welcome!
When converting stack traces between Firefox and Chrome that include eval frames, at least one frame is guaranteed to contain
undefinedas its frame type, name, or something else.As a temporary workaround, these faulty frames are being removed entirely during conversion.
But, this isn't ideal. The goal in future versions is to make the conversion more seamless, contribution is welcome!