Bug 168835 - Web Inspector: Implement a policy to age-out script/DOM breakpoints
Summary: Web Inspector: Implement a policy to age-out script/DOM breakpoints
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-24 11:27 PST by Matt Baker
Modified: 2017-03-07 22:34 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Baker 2017-02-24 11:27:55 PST
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.
Comment 1 Matt Baker 2017-02-24 11:28:35 PST
(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".
Comment 2 Joseph Pecoraro 2017-02-24 17:20:43 PST
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.