[Webkit-unassigned] [Bug 118328] Optimize addStrackTraceIfNecessary to be faster in the case when it's not necessary

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 9 10:38:53 PDT 2013


--- Comment #17 from Chris <chris_curtis at apple.com>  2013-07-09 10:40:55 PST ---
For both cases, the frame that is being removed is the allocated memory that has not been fully built because there was the error thrown. For decode and eval at the time to creation, the stack trace is still pointing to the unfinished frame. The result is an added frame at the top that looks like decodeURI@[native code] and eval@[native code] with the rest of the stack matching the expected results from Safari, FireFox, and Chrome.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list