Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined
New issue 31516 by megazzt: No JavaScript call to trigger a heap snapshot
http://code.google.com/p/chromium/issues/detail?id=31516
Google Chrome 4.0.266.0 (Official Build 33992)
WebKit 532.6
V8 2.0.3.1
User Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
AppleWebKit/532.6 (KHTML, like Gecko) Chrome/4.0.266.0 Safari/532.6
What steps will reproduce the problem?
1. Use for (var i in console) { console.log(console[i]); } to dump the list
of supported functions;
2. Note the lack of a function to take a heap snapshot (and I'm not sure
where else one would be.)
What is the expected result?
There should be a function such as console.takeHeapSnapshot
What happens instead?
There is no such function.
Please provide any additional information below. Attach a screenshot if
possible.
A workaround is to use the debugger keyword to suspend JavaScript execution
, take a snapshot by hand, and then resume but I can see this getting old
fast.
Since console appears to be implementing the Firebug Console API perhaps
you might not want to add more functions there, but you already have a
.markTimeline so I figure this is unlikely.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
