还有人遇到过 Eclipse 3.4 with Flex Builder 由于 OOME 不断崩溃的情况吗？
首先我应该说我对配置 Eclipse 内存设置非常熟悉。 我目前正在使用已发布配置之一的变体：
... --launcher.XXMaxPermSize 256米 -vmargs -Xms40米 -Xmx512米 -Xss2m -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote
根据 JConsole 和内部堆监视器，Eclipse 永远不会耗尽堆。
它所做的就是不断地因 OOME 崩溃，比如每 30-50 分钟一次。 有时它告诉我有 OOME，有时它只是默默地关闭。 奇怪的是，一直运行的另一个 eclipse 实例（J2EE 版本）从未崩溃过一次，即使有更多的源文件。
有一次或两次崩溃后它变成了僵尸进程，我看到了它的内存占用量 - 大约 1.5gigs，远高于堆监视器所说的它正在使用的内存占用量。 那么，到底是怎么回事呢？ 有东西漏吗？ 我确实注意到活动线程的数量似乎不断增加。
有人遇到过这个问题并解决了吗？
I should first say that I'm pretty familiar with configuring Eclipses memory settings. I'm currently using a variant of one of the posted configurations:
...
--launcher.XXMaxPermSize
256m
-vmargs
-Xms40m
-Xmx512m
-Xss2m
-Djava.net.preferIPv4Stack=true
-Dcom.sun.management.jmxremote
And according to JConsole and the internal heap monitor, Eclipse never gets close to running out of heap.
What it DOES do is crash constantly with OOMEs, like every 30-50 minutes. Sometimes it tells me there was an OOME, other times it just closes silently. Strangely, the OTHER eclipse instance that is running all the time (the J2EE version) has never crashed once, even with a lot more source files.
There's been once or twice where it's been a zombie process after the crash and I got to see its memory footprint - around 1.5gigs, well above what the heap monitor said it was using. So, what's the deal? Something leaking? I do notice that the number of active threads appears to constantly go up.
Anyone had this problem and fixed it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
根据 此站点，Eclipse/Flex Builder 的正确内存设置是
：我用于 Eclipse 的内存设置似乎工作正常。 希望有帮助。
According to this site, the proper memory settings for Eclipse/Flex Builder is:
Those are the mem settings I use for eclipse and it seems to work fine. Hope that helps.
根据项目的大小和复杂性，您可能需要增加分配给 FlexBuilder 的内存。 您可以尝试使用不同的 JVM。 如果 Flexbuidler 无法启动，那么您可能给了它太多的内存。
这个问题没有圣杯，但分享我的 FlexBuilder.ini 可能会有所帮助：
Depending on the size and complexity of the project you may have to raise the memory given to FlexBuilder. You may try using different JVM. In case Flexbuidler won't start up then you probably give it too much memory.
There is no holy grail for this problem, but sharing my
FlexBuilder.inimay help some: