为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Memory leak / Handle leak

  • 1 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 la3amon

more options

When my Webroot comes back with its scan report it always says that "an active process has a possible handle leak" and "an active process has a possible memory leak". What's that all about? I am not a techie, so please explain. It doesn't sound very reassuring, does it?

When my Webroot comes back with its scan report it always says that "an active process has a possible handle leak" and "an active process has a possible memory leak". What's that all about? I am not a techie, so please explain. It doesn't sound very reassuring, does it?

被采纳的解决方案

Hi angus7,

Here is a fairly simple explanation for a memory leak: A Memory leak occurs when your computer closes an open program and that program fails to release whatever memory it used while running. A memory leak may also happen when an object is stored in memory but cannot be accessed by the running code. It's basically a type of bug in a program. Nothing really to worry about. These events happen frequently and can sometimes affect performance. If a certain program is causing an issue which greatly affects your system resources or crashes frequently, you should submit a bug report to the authors of the offending program. One way to check for memory leak is to press and hold down your Windows key and tap the Pause/Break key to bring up System Properties. Most keyboards no longer have a Pause/Break key so you would have to look up the keyboard shortcut for your system.

定位到答案原位置 👍 1

所有回复 (1)

more options

选择的解决方案

Hi angus7,

Here is a fairly simple explanation for a memory leak: A Memory leak occurs when your computer closes an open program and that program fails to release whatever memory it used while running. A memory leak may also happen when an object is stored in memory but cannot be accessed by the running code. It's basically a type of bug in a program. Nothing really to worry about. These events happen frequently and can sometimes affect performance. If a certain program is causing an issue which greatly affects your system resources or crashes frequently, you should submit a bug report to the authors of the offending program. One way to check for memory leak is to press and hold down your Windows key and tap the Pause/Break key to bring up System Properties. Most keyboards no longer have a Pause/Break key so you would have to look up the keyboard shortcut for your system.