Major changes were introduced with the new run/debug setup in 0136, and one
of them causes sketches to not run every ~10th time or so (this will vary
depending on your machine). Hitting Run again should make things start up.

The problem has been tracked to the join() calls inside Runner.java,
however the exact problem is unclear.

This may actually be a problem with Mac OS X sometimes not launching Java
correctly (the runner launches a new Java VM when Run is pressed). More
recent Java releases for Mac OS X have become less stable.

*** Bug 782 has been marked as a duplicate of this bug. ***

Sorry to inform, but this seems to be pervasive on WinXP (pro, sp2) with 0136 +
bundled jre. Every sketch I've tried (even from a fresh restart to a brand new one-
liner: println("hello"); ) even after multiple restarts and reboots, consistently fails to
run and generates:

Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError:
com/sun/jdi/connect/VMStartException
at processing.app.Editor.handleRun(Editor.java:1147)
at processing.app.EditorToolbar.mousePressed(EditorToolbar.java:321)
at java.awt.Component.processMouseEvent(Component.java:5514)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3135)
at java.awt.Component.processEvent(Component.java:5282)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3984)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.LightweightDispatcher.retargetMouseEvent
(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent
(Container.java:3889)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1791)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

nah, that's bug #780, which has been fixed in 0137 (which was just
uploaded). give it a shot...

To be clear for anyone who might come across this bug:

This bug report refers to when you hit run, and nothing happens--no
exception, no nothing. The problem is generally intermittent, however I
wouldn't be surprised if on some machines (particularly very fast or very
slow ones) it happens /all/ the time.

If you're getting an exception when run is pressed, please file a new bug.

This also seems to be isolated to cases where the sketch being started is
not the "main" window, or the first window that was used in the
application; which is a helpful clue and hopefully means I'm close to
finding a fix.

*** Bug 784 has been marked as a duplicate of this bug. ***

Whups, comment #6 is wrong, the "main window" issue is now being tracked at
bug #784.

This bug so far seems to be Mac-only. Even though bug #782 has been marked
as a dupe of this one, i think bug #784.

*** Bug 799 has been marked as a duplicate of this bug. ***

On mac os x I add an entry to the host database via netinfo utility .
In the entry I assign the name of the machine to 127.0.0.1. all seems work fine

Bug still persists in Processing 0140.

System Info:
Leopard (10.5.3)

Darwin Macintosh-4.local 9.3.0 Darwin Kernel Version 9.3.0: Fri May 23 00:51:20 PDT 2008;
root:xnu-1228.5.18~1/RELEASE_PPC Power Macintosh
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

yes, it will persist until the bug has been marked "FIXED" instead of
"ASSIGNED".

Bug persists with Processing 0141

System Info:

Mac OS X 10.5.3, PPC

Darwin Macintosh-4.local 9.3.0 Darwin Kernel Version 9.3.0: Fri May 23 00:51:20 PDT 2008;
root:xnu-1228.5.18~1/RELEASE_PPC Power Macintosh
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

Please stop posting that, I'm well aware that the bug still persists. Once
again, that's why it's marked "ASSIGNED" and not "FIXED". As soon as it's
fixed, the status will change, and the fix will be noted in revisions.txt
with the subsequent release.

I'm closing this bug as a dupe because it's become a complete mess. If
you're getting "Target VM failed to initialize: VM initialization failed"
when you hit Run, you want Bug #796.

If you're getting an intermittent problem, with *no* error message, then
you may be dealing with Bug
#852 since I'm guessing that it's not the same as what any of you are
dealing with.

*** This bug has been marked as a duplicate of 852 ***

for people having the "Target VM failed to initialize: VM initialization
failed" problem, i may have a fix, see bug #796 for more info (and add
yourself as a cc if you want to track the status).