FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 783 : Nothing runs in 0136 or 0137 on Mac OS X (Leopard)
Last modified: 2008-06-02 09:35
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
DUPLICATE of bug
784
Pr
i
ority:
P2
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
TomC
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2008-05-30 12:03
Nothing would run (none of the examples, none of my own sketches, with
buttons or with shortcuts) using Processing 0136 or 0137 on Mac OS X 10.5.2
(Leopard) on a Macbook Pro.
As far as I can remember I've not messed with the default Java install.
Here's what it reports:
tom% java -version
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)
Digging into Processing.app it references $JAVAROOT, however it seems that
JAVAROOT isn't set on my system.
So I tried this:
tom% echo $JAVAROOT
tom% which java
/usr/bin/java
tom% export JAVAROOT=/usr/bin/java
tom% echo $JAVAROOT
/usr/bin/java
tom% ./Processing\ 0137.app
And then sketches would run and things would export just fine. Hooray! A
workaround.
Let me know if there's anything else you'd like me to try.
(I did get one error with exporting after that but I haven't been able to
reproduce it so far.)
Additional Comment
#1 From TomC 2008-05-30 12:36
I've just realised that the JAVAROOT I added there doesn't really make any
sense. If anyone else is reading this thread, please don't assume that I
knew what I was doing, I think I was just lucky.
Additional Comment
#2 From fry 2008-05-30 13:26
k, i'll fire up my leper partition and see what i can find. $JAVAROOT is
something defined by the macos launcher, it's not an environment variable,
but clearly something has gone awry.
Additional Comment
#3 From fry 2008-05-30 13:50
hm, just tried on my own machine running 10.5.2 and it runs fine.. thought
it might be missing dev tools but i tried on a 10.4.11 machine w/o dev
tools and that seems to be ok.
does console.app show any error messages? does processing itself run, just
not the actual sketches?
Additional Comment
#4 From fry 2008-05-30 15:58
could this in fact be
bug #784
?
Additional Comment
#5 From ewjordan 2008-05-30 17:24
I can confirm this on 10.5.2, and it does indeed appear to be
bug #784
, at
least as far as I can tell - the sketch that's open when the program opens
will run, but once you open a new one nothing happens.
FWIW, the app runs fine (well, sort of - the menus are REAL slow, and I get
the spinning beach ball a lot), and nothing shows up in the console (either
the Processing console or the system log).
Additional Comment
#6 From fry 2008-05-31 09:14
k, i'll mark it as a dupe unless i hear otherwise.
*** This bug has been marked as a duplicate of
784
***
Additional Comment
#7 From Ira 2008-06-02 09:09
(In reply to
comment #6
)
>
>
>
> Additional
Comment #6
From
> fry
> 2008-05-31 09:14
>
> <!--
> addReplyLink(6); //-->[reply]
>
>
>
>
> k, i'll mark it as a dupe unless i hear otherwise.
>
> *** This bug has been marked as a duplicate of 784 ***
>
>
[quote]
FWIW, the app runs fine (well, sort of - the menus are REAL slow, and I get
the spinning beach ball a lot)
[/quote]
This has been the case for me since 0136 through 0138 (OS X 10.5.2). Its
worse than slow though?usually leading to a force quit
Additional Comment
#8 From Ira 2008-06-02 09:18
(In reply to
comment #4
)
>
>
>
> Additional
Comment #4
From
>
> fry
> 2008-05-30 15:58
>
> <!--
> addReplyLink(4); //-->[reply]
>
>
>
>
> could this in fact be
bug #784
?
>
>
processing/sketches runs fine for me; it's just the top menu issue:
some console messages:
launch 0135:
6/2/08 12:14:25 PM [0x0-0x37037].org.processing.app[413] [JavaAppLauncher]
JVMArchs not found in Java dictionary
launch 0138
6/2/08 12:15:08 PM [0x0-0x39039].org.processing.app[417] [JavaAppLauncher]
A 64-bit JVM is available for 1.5.0
Additional Comment
#9 From fry 2008-06-02 09:35
menu issue is
bug #786
. this bug has been fixed and closed.