Bug 78574
| Summary: | Web Inspector: Typed Arrays not sized correctly in heap snapshots | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ben Vanik <ben.vanik> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Major | CC: | alph, apavlov, bburg, ben.vanik, bweinstein, joepeck, kbr, keishi, loislo, michaelbraithwaite, pfeldman, pmuellr, rik, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=157945 | ||
Ben Vanik
While trying to find the discrepancies between Task Manager and the heap snapshot panel in the Chrome dev tools I noticed that typed arrays are not getting their size counted correctly. It looks like only the Javascript side of the arrays are counted, and not the native backing store. This means that if one has a 1MB Float32Array they'll only see it as ~32B in the heap profile. In applications making heavy use of typed arrays this makes the heap profiles largely useless for identifying memory hogging code. It's not enough of a workaround to use the count of typed arrays as an indicator of size as a large application will use thousands of arrays varying from 32B to several MB each.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
michaelbraithwaite
See also http://code.google.com/p/chromium/issues/detail?id=129729
michaelbraithwaite
https://bugs.webkit.org/show_bug.cgi?id=61792 is a superset of this.