Eclipse with the ADT runs fine for me on Ubuntu 12.04 64-bit. However, whenever I plug in my phone with Eclipse open, it tends to hang and max out my CPU for an indefinite amount of time. Even when it doesn't hang immediately after plugging in my phone, it will intermittently seize up and not respond to any input for anywhere from a minute to 10+ minutes if the phone is at all connected. When run 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 researching these errors, I believe this is not the root cause as Eclipse does this even when my phone isn't connected and it runs fine.
The logs are similarly useless and only mention that the workspace wasn't saved after I am forced to shut down Eclipse.
For reference, the phone I am connecting is a Droid 2 Global running Android 2.3.4.
Bugs when dealing with ADT + Eclipse are common.
Update to the latest ADT and this must be fixed
I'm using my phone as well, to debug with the latest ADT and am facing no problems.
I see you are running 64bit Ubuntu... I had similar issue under 64bit Debian 7 (Wheezy) and solved it by running 32bit Eclipse Juno under 32bit Java 1.7.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With