[Webkit-unassigned] [Bug 23551] Crash on page load with profiler enabled and running

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 29 11:23:31 PST 2009


cwzwarich at uwaterloo.ca changed:

           What    |Removed                     |Added
                 CC|                            |cwzwarich at uwaterloo.ca

------- Comment #12 from cwzwarich at uwaterloo.ca  2009-01-29 11:23 PDT -------
> I don't understand how you could trigger this problem just by loading
> about:blank, since you shouldn't execute any JavaScript, let alone
> Interpreter::execute(FunctionBodyNode*,...), which only gets called for special
> direct invocations of functions, like event handlers.

I assumed it was due to the code that the profiler executes when a page loads.

> The best solution is probably to pass "callFrame" rather than "newCallFrame" to
> the profiler.

Won't that give the profiler the wrong lexical global object in some cases,
giving the profiler the wrong profile group? Is that a problem? All
fast/profiler tests pass and the crashes goes away.

I still don't understand the difference between Debug and Release.

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

More information about the webkit-unassigned mailing list