Eclipse Timeout Error from Debugger?

Question

I use Eclipse to develop Android applications. Everything seems to be going smoothly while I'm debugging, and then Eclipse seems to hang up - the error is "Not responding." I looked at the log files and I get this timeout error every 3 seconds. Has anyone else seen this?

I need to restart the machine.

!ENTRY org.eclipse.jdt.debug 4 125 2014-03-12 10:18:19.417 !MESSAGE Internal error logged from JDI Debug: !STACK 0 org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 12963. at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:186) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:197) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:226) at org.eclipse.jdi.internal.VirtualMachineImpl.classesBySignature(VirtualMachineImpl.java:638) at org.eclipse.jdi.internal.VirtualMachineImpl.classesByName(VirtualMachineImpl.java:667) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.jdiClassesByName(JDIDebugTarget.java:1596) at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.filterUnloadedTypes(JavaHotCodeReplaceManager.java:348) at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.notifyUnsupportedHCR(JavaHotCodeReplaceManager.java:379) at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager$2.run(JavaHotCodeReplaceManager.java:322) at org.eclipse.debug.core.DebugPlugin$AsynchRunner.run(DebugPlugin.java:1068) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.core.DebugPlugin$AsynchRunner.async(DebugPlugin.java:1051) at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:405) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SESSION 2014-03-12 10:30:21.771 ----------------------------------------------- eclipse.buildId=M20130204-1200 java.version=1.7.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86_64 

Answer 1

You need to run -clean and then use Task Manager (on Windows) to stop adb.exe. Once you do this, everything will go smoothly.

Answer 2

I suggest you clear your eclipse using a terminal

Mine catalog

 cd /Applications/eclipse_juno/Eclipse.app/Contents/MacOS 

Clear command

 ./eclipse -clean 

OR

Open eclipse.ini in the eclipse folder.

Change this line

 -Xms512m -Xmx1024m 

in that

 -Xms768m -Xmx768m eclipse.ini -startup ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20120913-144807 -product org.eclipse.epp.package.jee.product --launcher.defaultAction openFile -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Dosgi.requiredJavaVersion=1.5 -Dhelp.lucene.tokenizer=standard -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=192m -Xms768m -Xmx768m -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts 

If still happening, restart your computer.

http://blog.revivalx.com/2014/03/15/your-eclipse-always-crash-how-to-fix-and-enhance-to-do-list/

Answer 3

You can increase debug time in Eclipse.

Go to the / Preferences window. In Java / Debug, you will see the debugger debugging option.

Answer 4

Deselect window-> Settings-> Java-> Debug, "Pause execution on uncaught exceptions"