Bug 168835
| Summary: | Web Inspector: Implement a policy to age-out script/DOM breakpoints | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Matt Baker <mattbaker> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, joepeck |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Matt Baker
Summary:
Implement a policy to age-out script/DOM breakpoints. Saved breakpoints that will never be encountered again are wasting space in the WebInspector.Setting. This affects both script and DOM breakpoints, but the latter is slightly worse in that those are all sent individually to the backend when the inspector opens.
Proposal:
Associate each breakpoint with a timestamp that is updated whenever the breakpoint resolves. When breakpoints are loaded, "expired" breakpoints should be removed. A dual policy could also be implemented wherein the breakpoint store has a maximum size, and we trim the oldest breakpoints when we approach the limit.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Matt Baker
(In reply to comment #0)
> Summary:
> Implement a policy to age-out script/DOM breakpoints. Saved breakpoints that
> will never be encountered again are wasting space in the
> WebInspector.Setting. This affects both script and DOM breakpoints, but the
> latter
Should be "the former".
Joseph Pecoraro
There are plenty of other URL-hash based settings that we should investigate aging out as well. Like remembering whether or not a particular folder is expanded or not on a particular domain.