[Webkit-unassigned] [Bug 92198] Web Inspector: [JSC] debugging long-running scripts with conditional breakpoints consumes huge amounts of memory

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=92198


Peter Wang <peter.wang at torchmobile.com.cn> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |peter.wang at torchmobile.com.
                   |                            |cn




--- Comment #2 from Peter Wang <peter.wang at torchmobile.com.cn>  2012-12-13 00:28:10 PST ---
This problem is more obvious in memory-limited environment (e.g. mobile).

The root reason is that, for failed condition of breakpoint, JSC doesn't run the EventLoop, so in a dense loop of js code, there is no chance to recycle garbage caused by evaluating the breakpoint's condition.

There is an interesting test. if you put a normal breakpoint after the breakpoint with failed condition, the GC is working well. Since for a success breakpoint JSC run an EventLoop.

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