Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

Screenshot sprint: JavaScript Memory Profiling #46

Closed
addyosmani opened this issue Jan 15, 2014 · 1 comment
Closed

Screenshot sprint: JavaScript Memory Profiling #46

addyosmani opened this issue Jan 15, 2014 · 1 comment
Assignees
@addyosmani

Comments

@addyosmani
Copy link
Member

Compare the current screenshots in memory profiling to the Canary DevTools and find out what has changed. We'll want to drop docs for any features that were removed.

Doc: https://developers.google.com/chrome-developer-tools/docs/javascript-memory-profiling
@ghost ghost assigned addyosmani Jan 15, 2014
@paulirish paulirish mentioned this issue May 16, 2014
Closed
@paulirish
Copy link
Member

duping this into #44

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@addyosmani addyosmani

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paulirish @addyosmani