From 5d5a5841c820a26bbaa7ceb393d0e8ce1ca09ad4 Mon Sep 17 00:00:00 2001 From: David Fokkema Date: Tue, 15 Apr 2014 20:50:30 +0200 Subject: [PATCH] Do not wait for debugger to start running sketch By default, the java VM is started with options for attaching a remote debugger. The sketch is suspended until the remote debugger connects. This always succeeds the first time a sketch is run. At least on OS X 10.9, this seems to be very fragile, and successive runs of the sketch often fail to start. This commit tells the VM to *not* wait for the debugger before starting the sketch. Fixes processing#2402 --- app/src/processing/mode/java/runner/Runner.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/processing/mode/java/runner/Runner.java b/app/src/processing/mode/java/runner/Runner.java index 9bea617b5..887266d6e 100644 --- a/app/src/processing/mode/java/runner/Runner.java +++ b/app/src/processing/mode/java/runner/Runner.java @@ -133,7 +133,7 @@ public class Runner implements MessageConsumer { // String jdwpArg = "-Xrunjdwp:transport=dt_socket,address=" + portStr + ",server=y,suspend=y"; // String debugArg = "-Xdebug"; // Newer (Java 1.5+) version that uses JVMTI - String jdwpArg = "-agentlib:jdwp=transport=dt_socket,address=" + portStr + ",server=y,suspend=y"; + String jdwpArg = "-agentlib:jdwp=transport=dt_socket,address=" + portStr + ",server=y,suspend=n"; // Everyone works the same under Java 7 (also on OS X) String[] commandArgs = new String[] { Base.getJavaPath(), jdwpArg };