Eclipse 在调试时挂起
我搜索了很多关于这个主题的内容，但找不到合适的解决方案。
我使用的是 eclipse 3.6 Helios 版本，操作系统为 fedora15。在我的应用程序中，我使用 GWT2.4 进行前端开发。
现在，当我使用调试模式并希望在某个时刻进行调试时，Eclipse 会挂起 3-4 分钟。它会在之后恢复并再次开始调试过程。
我在 Windows 上使用了过去 3 年的 Eclipse，但没有遇到这个问题。在 Fedora 中，我在过去 4 个月中使用它，据说这个问题是在过去一个月发生的。
我不明白 eclipse 有什么问题。 请帮帮我。 提前致谢。
I searched lot about this topics but can't find a proper solution.
I am using eclipse 3.6 Helios version with operating system fedora15. In my application I am using GWT2.4 for front end development.
Now while I work with debug mode and want to debug at some point at the same time eclipse hangs for 3-4 mins.It resumes after and again start to debug process.
I am using this eclipse from last 3 years with windows but not faced this issue.In fedora I am using it from last 4 months and this problems stated to occur from last one month.
I am not getting what is the issues with eclipse.
Please help me out.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
这是不同项目/代码中发生的情况，还是导致冻结的相同代码？我遇到过线程在后台启动并导致问题的问题。
你说“（...）挂起 3-4 分钟。它会在之后恢复并再次开始调试过程。”，你是什么意思？它是否继续调试并移至下一行，或者是否发生崩溃并重新启动？
您有多久没有更换工作空间了？随着时间的推移，我发现这是一个问题，而不是 Eclipse 安装。创建一个新的工作区文件夹，导出所有项目和首选项并重新开始。
Is this something that happens with different projects/code, or is it the same code that causes freezes? I've had issues where threads have started in the background and caused problems.
You say "(...) hangs for 3-4 mins.It resumes after and again start to debug process.", what do you mean? Does it continue to debug and move to the next line, or is there a crash and it restarts?
How long has it been since you changed workspace? I've found this, rather than the Eclipse installation, to be an issue over time. Create a new workspace folder, export all your projects and preferences and start fresh.
您正在使用 GWT 2.4，我认为您也可能正在使用 UI.xml...顶部的每个 ui.xml 中有一个标记，例如
这意味着 eclipse 每次都会获取该 xhtml.ent 文件，并且有GWT eclipse 插件中的问题请查看下面的链接
http://code.google.com/p/google-web-toolkit/issues/detail?id=5265
有一条评论说
尝试一下并告诉我。
You are using GWT 2.4 and I think you might be working with UI.xml too... There is a tag in each ui.xml at the top like
Which means eclipse is going to get that xhtml.ent file each time and there is a issue in GWT eclipse plugin have a look to below link
http://code.google.com/p/google-web-toolkit/issues/detail?id=5265
There is one comment which says
Try it out and let me know.
我在必须使用功能较弱的笔记本电脑上遇到了完全相同的问题。
尝试以下方法之一
I had experienced the exact same problem on a less-powerful notebook I had to use.
Try one of the following
听起来您正在体验最新 Eclipse 架构的功能。在最新版本的 Eclipse 中，我注意到安装的插件和附加组件越多，环境运行速度就越慢。有很多关于新平台上的性能的类似帖子，
我已经删除了除我正在使用的插件之外的所有内容，并且从不在 Eclipse 环境中安装任何不需要的东西。
It sounds like you are experiencing the features of the latest Eclipse arch. In the latest versions of Eclipse I have noticed that the more plugins and add-ons you have installed, the slower the environment runs. There are a lot of similar posts regarding performance on the new platform
I have removed all but the plugins I am using and never install anything not needed into the Eclipse environment.
我“可能”有过这样的经历。没有把握。突然又开始工作了。每次尝试调试应用程序时，在创建“表”元素的代码部分（GWT 内部）中，我都会遇到困难。可能有些事情只需要一段时间，当它发生时你只需要“等待”。去喝杯咖啡，打字。不管怎样，我已经深入研究了 GWT 代码，所以我确信这是某种 GWT 问题。
我认为这可能是日志系统中的某种无限递归（例如记录器代码意外地尝试记录自身，然后进入循环？）。另外，有 50/50 的可能性是，它只是单击“运行”而不是“调试”，使其再次开始工作。因此，如果您遇到问题，至少尝试一下。我的直觉和 30 年的编程经验告诉我，这与记录器有关。我可以排除“计算机速度慢”的可能性，因为在我购买一台新机器（戴尔 XPS、酷睿 i7、8 GB 内存和大容量磁盘）之前，我从未遇到过这种情况。所以我不会责怪硬件或 Eclipse 的膨胀。
I "may" have experience this. Not sure. Suddenly started working again. I was getting a hang every time I would try to debug an app, in the part of the code (inside GWT) that creates a "table" element. Could be that there is something that just takes a while and you just have to "wait it out" the when it happens. Go get a cup of coffee, type thing. anyway I HAD stepped deep into the GWT code, plenty so I'm convinced it IS a GWT issue of some kind.
I was thinking it was some infinite recursion possibly in the logging system (like logger code accidentally trying to log itself, and going into loop?). Also there's a 50/50 chance that it was simply clicking on 'run' instead of 'debug' made it start working again. So at least try that if you have problems. My gut instinct and 30yrs programming under my belt tells me it's logger related. I can rule out "slow computers" because I never had this happen until I got a new machien which is Dell XPS, Core i7, 8 GB ram, and massive disk. So I wouldn't blame hardware, or Eclipse bloat.