[Webkit-unassigned] [Bug 109723] New: Web Inspector: Should not let it's own memory usage show up in stats
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Feb 13 11:45:54 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=109723
Summary: Web Inspector: Should not let it's own memory usage
show up in stats
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: gman at chromium.org
CC: keishi at webkit.org, pmuellr at yahoo.com,
pfeldman at chromium.org, yurys at chromium.org,
apavlov at chromium.org, loislo at chromium.org,
vsevik at chromium.org,
web-inspector-bugs at googlegroups.com
Currently the memory timeline for a simple loop like
function init()
{
var ref = window.setInterval(function() { draw(); }, 50);
}
function draw()
{
return true
}
shows lots of memory usage. That memory usage is from dev tools which makes it kind of hard for developers to reason about their apps.
Is there some say devtools memory usage can be separated from user app memory usage? Switch allocators when entering dev tools code or switch kind of category that you can ignore for dev tools code?
See: http://stackoverflow.com/questions/14034107/does-javascript-setinterval-method-cause-memory-leak/
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list