[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





--- Comment #6 from Yury Semikhatsky <yurys at chromium.org>  2012-12-13 01:19:46 PST ---
(In reply to comment #2)
> 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.
> 
It sounds weird that the issue is specific to breakpoint conditions. How does it work in case of eval producing a lot of garbage in a tight loop in user code?



> 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.