Why does Eclipse + ADT plugin keep the CPU at 100%

Question

The second I open up layout.xml file from a simple skeleton app in Eclipse example plugin, the cpu usage locks up to 25% IE. 1 full core. and it's been on like this for the last 30minutes I wanted to let him run a longer time because I thought it is working something in the background but it just keeps doing that.

I've tested this on 2computers so far and the setup is install Android SDK, install Eclipse IDE for Java Developers, install ADT plugin: http://dl-ssl.google.com/android/eclipse/ open new project, select a skeleton project for Android 2.3.3 and just open the layout skeleton activity and perhaps change to android 2.3.3 in the upper right corner and maybe setup to theme.black.noTitleBar.Fullscreen.

And now your processor should be hitting 100% ( on one core ) and should be locked like that from now on.

Is there any solution to this issue, because at home I only have 1 core and I can not work on anything.

Does any one have any clue as to why this is happening ? http://my.jetscreenshot.com/demo/20110517-gbr8-201kb

Answer 1

I'm seeing the same issue so I filed a bug report at http://code.google.com/p/android/issues/detail?id=18865.

The Android team have now released a fix and it works for me. You have to upgrade to the latest revision of each SDK module that you downloaded through the android tool. The latest version of the ADT also has a number of fixed for long-standing issues.

Answer 2

I can't answer "Why" this happens. But I can say what fixes it.

I encountered this on Ubuntu 12.04 64 bit. I had 100% cpu and eclipse hang when I switched to debug view - Eclipse was unusable and had to kill it. I found the below bug report

https://code.google.com/p/android/issues/detail?id=34641

Following the comments there, I tried

cd /usr/lib/x86_64-linux-gnu/gtk-2.0/modules mv libgail.so libgail.so.moved

Eclipse did not hang (no 100% cpu) when I switched to debug view.