Hi,
TL;DR: I wrote a crude yet useful JS memory profiler. I told jimb
about it at the work week and am posting the details here in case it's
of interest to anyone.
Earlier this year I made some large memory usage improvements to
pdf.js
(https://blog.mozilla.org/nnethercote/2014/06/16/an-even-sli
On 12/8/14 2:28 PM, Boris Zbarsky wrote:
On 12/8/14, 3:18 PM, Chris Peterson wrote:
Are Firefox's JS throttling heuristics (e.g. for background tabs)
documented somewhere? Is this policy controlled by SpiderMonkey or Gecko?
The policy is controlled by Gecko.
The throttling policies are as fol
On 12/8/14, 3:18 PM, Chris Peterson wrote:
Are Firefox's JS throttling heuristics (e.g. for background tabs)
documented somewhere? Is this policy controlled by SpiderMonkey or Gecko?
The policy is controlled by Gecko.
The throttling policies are as follows:
1) Nested setTimeout/setInterval i
Are Firefox's JS throttling heuristics (e.g. for background tabs)
documented somewhere? Is this policy controlled by SpiderMonkey or Gecko?
In bug 1108483, the Shumway team is considering what the appropriate
user experience should be for SWF content scrolled off screen or in
background tabs.
4 matches
Mail list logo
