{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Anthone 的问题《How does JavaScript garbage collection work in Chr》','https://www.manongdao.com/q-904255.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Garbage collection is a behind-the-scenes language feature, so I'm assuming it's going to be slightly different in each browser and this question is specifically about Google Chrome.
How does Chrome's garbage collector work- what triggers it, can/should I manually trigger it, and (possibly out of scope for a single question) what patterns might cause memory leaks to get past it?