Components.utils.forceGC 编辑

Components.utils.forceGC lets scripts force a garbage collection cycle. The Mozilla JavaScript engine will perform garbage collection automatically when the JavaScript heap grows beyond a certain size. This mechanism doesn't account for any native (C++) XPCOM objects hanging off JavaScript objects though. In many cases a JavaScript application will have internal knowledge of JavaScript objects referencing large (trees of) XPCOM objects and know when they are no longer reachable. In this case it can be important to be able to force a garbage collection cycle from JavaScript.

Another instance where it can be useful to force garbage collection is before cleaning out dead reference from a hash of weak JavaScript references.

Users should note that garbage collection is a very expensive operation and should only be forced when it is known to be absolutely necessary.

Note: nsIDOMWindowUtils.garbageCollect() offers similar functionality but will trigger the cycle collector in addition to the garbage collector in the JavaScript engine. This will make sure that XPCOM components that build cycles with JavaScript objects also get collected which might be important, for example for testcases that depend on the garbage collector.

Requires UniversalXPConnect privileges.

If you want to schedule garbage collection to occur in the future, at a time when no JavaScript code is running, you can use Components.utils.schedulePreciseGC() instead.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:54 次

字数:1802

最后编辑:7年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文