Multiple versions of Chrome. Why Garbage Collection? Chapter 9 of Inside the Java Virtual MachineGarbage Collectionby Bill Venners The Java virtual machine's heap stores all objects created by a running Java application.
Objects are created by the new, newarray, anewarray, and multianewarray instructions, but never freed explicitly by the code. Garbage collection is the process of automatically freeing objects that are no longer referenced by the program. This chapter does not describe an official Java garbage-collected heap, because none exists. As mentioned in earlier chapters, the Java virtual machine specification does not require any particular garbage collection technique. Accompanying this chapter on the CD-ROM is an applet that interactively illustrates the material presented in the chapter. The name "garbage collection" implies that objects no longer needed by the program are "garbage" and can be thrown away. In addition to freeing unreferenced objects, a garbage collector may also combat heap fragmentation. Figure 9-1. Garbage Collection. Chrome Developer Tools. Command Line API. From FirebugWiki The Firebug Command Line provides these special functions for your convenience.
These include functions to control the Firebug UI, functions interacting with the page, shortcuts for selectors and shortcuts for the Console API. Other browsers implement the Command Line API as well; the Chrome DevTools, Safari Inspector and Opera Dragonfly, implement most of what is below.  help Returns a list of Command Line API commands including short descriptions.  $(selector) Returns a single element matching the given CSS selector.
Focus. Understanding Heap Profiler. Google Chrome's Heap Profiler and Memory Timeline. (with thanks to Mikhail Naganov for his feedback on the Developer Tools mailing list) Chrome’s Developer Tools contain some useful features for inspecting memory usage of a given page (and its change over time), but the documentation for these features is a bit sparse—and, if you are unfamiliar with these sorts of tools and what they do, their output can seem undecipherable.
Hopefully this brief post helps explain these features and what they can do for you. The Memory Timeline The memory timeline gives you an overview of memory usage over time. This makes it very easy to see how much memory various parts of your application use and can provide a strong visual cue if your application is leaking memory over time. The Heap Profiler The heap profiler is a somewhat more complicated tool than the memory timeline: while the memory timeline shows you how much memory is in use over time, the heap profiler gives you an overview of all of the objects in memory at the moment the snapshot was taken.
12 Tricks to Develop Quicker.