FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 1063 : PDE is not starting on Mac OS X ("CallStaticVoidMethod() threw an exception")
Last modified: 2008-11-29 08:37
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
FIXED -
Pr
i
ority:
P1
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
g00dnight
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2008-11-25 13:23
I'm start Processing 1.0 on Mac OS X (x86), and see only a menu with one item:
"Processing", and PDE window doesn't appear. There is also an error messages in console.log
which appears at this moment:
[JavaAppLauncher Error] CallStaticVoidMethod() threw an exception
Exception in thread "main" [JavaAppLauncher Error] CallStaticVoidMethod() threw an exception
Exception in thread "main"
Additional Comment
#1 From g00dnight 2008-11-25 13:39
i'm using mac os x 10.4.11
Additional Comment
#2 From fry 2008-11-25 13:40
move Home > Library > Processing > preferences.txt to the Desktop and then
try restarting the application. if that works, please attach a copy of the
broken preferences.txt file here so that i can see what went wrong.
Additional Comment
#3 From g00dnight 2008-11-25 21:46
(In reply to
comment #2
)
>
>
>
> Additional
Comment #2
From
>
> fry
> 2008-11-25 13:40
>
>
> addReplyLink(2); //-->[reply]
>
>
>
>
> move Home > Library > Processing > preferences.txt to the Desktop and then
> try restarting the application. if that works, please attach a copy of the
> broken preferences.txt file here so that i can see what went wrong.
>
>
After I moved preferences.txt to the Desktop I got the same result and same message in
console.log :( Also my java version is:
$ java -version
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-275)
Java HotSpot(TM) Client VM (build 1.5.0_16-132, mixed mode, sharing)
Additional Comment
#4 From ChuckEye 2008-11-26 22:26
Using same Java version under 10.5.5 works OK and does not generate any errors in the console
log.
Additional Comment
#5 From fry 2008-11-27 14:54
Hm, will try to get it to reproduce.
Additional Comment
#6 From fry 2008-11-27 19:11
Just for kicks, please try this version of pde.jar:
http://dev.processing.org/bugs/attachment.cgi?id=255
Use that file to replace the version found at:
Processing.app/Contents/Resources/Java/pde.jar
I'm not particularly convinced that it'll fix the problem, but it's worth a
try.
Additional Comment
#7 From g00dnight 2008-11-28 10:37
Now it works with new pde.jar, thanks! But I found that PDE also run with old pde.jar. Here is
the scenario:
1) Open any .pde file with Processing
2) PDE starts sucessfully
3) If you close Processing and try start it from a menu now you can see that PDE runs
successfully too, without any excetions in console.log
After that I was deleted preferences.txt, reinstalled Processing, replaced pde.jar with your file
and successfully started Processing from a menu.
Additional Comment
#8 From fry 2008-11-29 06:10
I don't quite follow what you mean. The problem no longer happens? Or
reinstalling fixed it? Or the previous version of pde.jar works but only if
you double-click the .pde file from a sketch?
Additional Comment
#9 From g00dnight 2008-11-29 06:57
>Or the previous version of pde.jar works but only if
> you double-click the .pde file from a sketch?
Previous version of pde.jar works only if I double-click the .pde file in Finder and after that
Processing also begins to run successfully if I start it from the dock (or Applications folder).
After I deleted Processing (and preferences.txt also) and then installed it again, the same
exception occurs when I start it from the dock (or Applications folder).
New version of pde.jar works fine even if I run Processing from Dock (or Applications folder)
right after install.
Additional Comment
#10 From fry 2008-11-29 07:17
Got it, thanks.
Additional Comment
#11 From fry 2008-11-29 08:35
***
Bug 1078
has been marked as a duplicate of this bug. ***
Additional Comment
#12 From fry 2008-11-29 08:37
Fixed for 1.0.1.