使用 Config 的 Java 内存泄漏

发布于 2024-12-11 03:02:23 字数 498 浏览 0 评论 0原文

我们使用下面的代码从 XML 读取配置值。我认为这可能会导致内存泄漏。

   // simulated code
   class ConfigReader {

      void matchPlanIDs() {
           ConfigurationItem[] items = ConfigurationHelper.getConfiguration("PLAN_IDS");
           // do something with here in for loop by reading from 
           // items[i].getTagVlue()...;  

           return;
      }
   }

items[] 是否在方法执行结束时引用了 ConfigurationHelper.getConfiguration("PLAN_IDS") 并且无法在一个周期内进行垃圾回收？这是一个强有力的参考吗？

感谢您的指点。

原文

We're using this below code to read config values from XML. I think it can cause a memory leak.

   // simulated code
   class ConfigReader {

      void matchPlanIDs() {
           ConfigurationItem[] items = ConfigurationHelper.getConfiguration("PLAN_IDS");
           // do something with here in for loop by reading from 
           // items[i].getTagVlue()...;  

           return;
      }
   }

Is items[] having reference to ConfigurationHelper.getConfiguration("PLAN_IDS") at the end of the method execution and can't be garbage collected in one cycle? Is this a strong reference?

Thanks for any pointers.

分享到QQ

分享到微博

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

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

随波逐流 2024-12-18 03:02:24

其本身

void matchPlanIDs() {
     ConfigurationItem[] items = ...
   return;
  }

不会导致内存泄漏。当然items将会被垃圾回收。

顺便说一句，最后的 return 也是毫无意义的。

如果您认为 ConfigurationHelper.getConfiguration(...) 导致内存泄漏，请尝试通过一个简单的示例来验证这一点。如果您确实注意到异常行为，可能最好向 ConfigurationHelper 的作者提交错误报告。但是，我怀疑这种情况不太可能发生，并且我怀疑您的内存消耗问题出在其他地方。

By itself,

void matchPlanIDs() {
     ConfigurationItem[] items = ...
   return;
  }

Cannot cause a memory leak. Of course items will be garbage collected.

By the way, the return at the end is also pointless.

If you think ConfigurationHelper.getConfiguration(...) is causing a memory leak, try to verify this by a simple example. If indeed you notice an abnormal behavior, probably it would be better to submit a bug report to the author of ConfigurationHelper. However, I suspect this case in unlikely, and I suspect your memory consumption problem lies elsewhere.

回复收藏 0 原文