Eclipse 崩溃并出现 GC 开销限制超出错误
这是我第一次使用 Proguard，我注意到如果您在 proguard-project.txt 中添加许多自定义规则，显然会花费更多时间来构建.这导致 Eclipse 崩溃报告 GC 开销限制超出 然后我不得不强制关闭 java，因为编辑器继续弹出错误和警报对话框.有什么办法可以避免 Eclipse 上的这些连续崩溃，从而解决报告的问题 这里也是?
It's the first time I am using Proguard, I've noticed that if you add many custom rules to proguard-project.txt it takes obviously much more time for building. That's cause Eclipse to crash reporting a GC overhead limit exceeded and then I have to force the shut down of java because the editor continues to pop out error and alert dialogs. Is there any way to avoid these continuous crashes on Eclipse and so fix the problem reported here too?
推荐答案
已修复，我阅读了所有其他论坛关于该问题的帖子，但没有人说如何在 Eclipse 上修复它.我找到了修复here
Fixed, I read all the others forum posts about the problem but no one said how to fix it on Eclipse. I found the fix here
如果链接失效，您可以执行以下操作.编辑eclipse.ini"，并设置类似的内容:
in case the link becomes dead, here's what you can do. Edit "eclipse.ini", and set something like that:
-XX:MaxPermSize=1024m
-Xms512m
-Xmx1024m
相关文章