Eclipse ADT bundle freezes when phone is connected

Question

Eclipse with ADT works fine for me on Ubuntu 12.04 64-bit. However, whenever I connect my phone to open Eclipse, it tends to hang and maximize my processor indefinitely. Even when it does not hang immediately after connecting my phone, it will periodically intercept and not respond to any input signal from a minute to 10+ minutes, if the phone is connected at all. When launched on the command line, this is the only output:

(ADT:11808): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed (ADT:11808): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 

etc...

After studying these errors, I believe that this is not the main reason, because Eclipse does this even when my phone is not connected and it is working fine.

Logs are equally useless and only mention that the workspace was not saved after I had to close Eclipse.

For reference, the phone I'm connecting to is Droid 2 Global running Android 2.3.4.

Answer 1

Errors when working with ADT + Eclipse are common.

Update to the latest ADT and this should be fixed

I also use my phone to debug the latest ADT and not run into problems.

Answer 2

I see that you are using 64-bit Ubuntu ... I had a similar problem under 64-bit Debian 7 (Wheezy) and decided to run it on 32-bit Eclipse Juno under 32-bit Java 1.7.

Answer 3

I have this problem - you need to clear the logcat buffer (error in adt).

before connecting the phone to the phone, open a terminal and run "adb logcat", this is not a 100% fix, but it reduces the number of failures. In addition, reducing the amount of log data generated by your application will help a lot (once again, too many logs are reset by the plugin).

Oddly enough, this was fixed shortly before Christmas, but was regressed after the next update.

In any case, I send an error message when I print this.