WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
168835
Web Inspector: Implement a policy to age-out script/DOM breakpoints
https://bugs.webkit.org/show_bug.cgi?id=168835
Summary
Web Inspector: Implement a policy to age-out script/DOM breakpoints
Matt Baker
Reported
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.
Attachments
Add attachment
proposed patch, testcase, etc.
Matt Baker
Comment 1
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".
Joseph Pecoraro
Comment 2
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.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug