Eclipse constantly locks/freezes during debugging on macOS.

[guw]

We noticed that Eclipse constantly freezes during debugging. It's unclear what is causing this. Remote debugging seems worse then debugging a process from within Eclipse directly. (Although it's technically the same.)

The application being debugged stays responsive.

Any ideas how to troubleshoot this?

Looking at the stack, the main thread is blocked in SWT code:

	at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
	at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:236)
	at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1147)

while the debug connection seems to be retrieving something:

"Packet Receive Manager" #656 daemon prio=5 os_prio=31 cpu=4689.55ms elapsed=2472.22s tid=0x0000000158633600 nid=0x1d127 runnable  [0x0000000a3d17a000]
   java.lang.Thread.State: RUNNABLE
	at sun.nio.ch.SocketDispatcher.read0([email protected]/Native Method)
	at sun.nio.ch.SocketDispatcher.read([email protected]/SocketDispatcher.java:47)
	at sun.nio.ch.NioSocketImpl.tryRead([email protected]/NioSocketImpl.java:266)
	at sun.nio.ch.NioSocketImpl.implRead([email protected]/NioSocketImpl.java:317)
	at sun.nio.ch.NioSocketImpl.read([email protected]/NioSocketImpl.java:355)
	at sun.nio.ch.NioSocketImpl$1.read([email protected]/NioSocketImpl.java:808)
	at java.net.Socket$SocketInputStream.read([email protected]/Socket.java:966)
	at java.net.Socket$SocketInputStream.read([email protected]/Socket.java:961)
	at java.io.DataInputStream.readInt([email protected]/DataInputStream.java:381)
	at org.eclipse.jdi.internal.connect.SocketConnection.readPacket(SocketConnection.java:82)
	- eliminated <owner is scalar replaced> (a java.io.DataInputStream)	at org.eclipse.jdi.internal.connect.PacketReceiveManager.readAvailablePacket(PacketReceiveManager.java:303)
	at org.eclipse.jdi.internal.connect.PacketReceiveManager.run(PacketReceiveManager.java:90)
	at java.lang.Thread.run([email protected]/Thread.java:840)

Everything else seems to be sleeping.

Questions I have:

• Is this a problem of the process being debugged not replying correctly?
• Is this a connectivity issue of the machine?

The problem seems to be only affecting Eclipse, though. Users of other IDEs are able to debug without issues.

jstack_eclipse.txt