Menu
I've built an application that wastes 40% of its time collecting garbage, and I'm at my wits' end trying to find out where it is coming from. I've corralled any possible problems in my own code, yet it persists. I'm beginning to suspect some third party code of being the problem, and I'd like to know if I can somehow track down what is being garbage collected. If there's a Chrome-specific answer, that'd be great, but I'll take anything at this point.
250
You normally can't tell whether an object has been garbage collected by using some reference to the object–because once you have a reference to the object, it won't be garbage collected. You can instead create a weak reference to an object using the WeakReference object.
Some high-level languages, such as JavaScript, utilize a form of automatic memory management known as garbage collection (GC). The purpose of a garbage collector is to monitor memory allocation and determine when a block of allocated memory is no longer needed and reclaim it.
JavaScript automatically collects the information of the unmercenary memory blocks and removes them from the memory. The garbage collector searches for reachability from the root object to determine whether an object will be used in the future or not.
Reference Counting Garbage Collection in JavaScript It determines whether the value still has any object referencing it. If the object has zero references pointing to it, that object is said to be “garbage”. The garbage collector detects these objects and releases them from memory.
In Chrome I would start with following:
Following links may be useful:
141
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
