[Webkit-unassigned] [Bug 92198] New: Web Inspector: 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

           Summary: Web Inspector: debugging long-running scripts with
                    conditional breakpoints consumes huge amounts of
                    memory
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.7
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: felixcca at yahoo.ca
                CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    bweinstein at apple.com, apavlov at chromium.org,
                    loislo at chromium.org


When uninterrupted, long-running scripts execute under the Javascript debugger, and those scripts have conditional breakpoints, WebProcess will consume huge amounts of memory for seemingly little reason.

On the test case attached, with the conditional breakpoints, memory consumption continually grows to the point where there's no more free memory available. With the conditional breakpoints off, memory usage remains about stable.

STEPS TO REPRODUCE
1. Launch the attached web page
2. Open the Web inspector, start the debugger
3. Add 4 conditional breakpoints, one per line inside the `for` loop of the `foo` function, and give them an unlikely condition (`i == -1` for instance)
4. With your favorite diagnostics tool, watch WebProcess eat up all the memory it can

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