When running any example which uses pushMatrix I get the following console
output:

frame: processing.core.PGraphics3D:2721 in thread instance of
java.lang.Thread(name='Animation Thread', id=489)
frame: processing.core.PApplet:7208 in thread instance of
java.lang.Thread(name='Animation Thread', id=489)
frame: Ortho:51 in thread instance of java.lang.Thread(name='Animation
Thread', id=489)

Exception in thread "Animation Thread" java.lang.NullPointerException
at processing.core.PGraphics3D.pushMatrix(PGraphics3D.java:2721)
at processing.core.PApplet.pushMatrix(PApplet.java:7208)
at Ortho.draw(Ortho.java:51)
at processing.core.PApplet.handleDraw(PApplet.java:1405)
at processing.core.PApplet.run(PApplet.java:1310)
at java.lang.Thread.run(Thread.java:613)

Is seems modelviewStack in PGraphics3D is null.

This happens with r4301 from svn.

Uncommenting lines 265 and 267 in PGraphics3D.java seems to solve it. Is
there any reason why somebody commented them out?

I am running on Mac OS X 10.4.11

Use a tagged release instead of the ones out of subversion. I'm in the
middle of working on that.

I would if they worked.

Spare me the drama. You just downloaded this software for free. You're
getting free support. You're not owed anything. If you don't like how
things work, please go away--I don't need random strangers being rude in my
inbox.

Sorry for the long text:
Wow, i thought you were a little pissed after reading your first reply, but
i didn't expect that.
I am sorry if i said something rude. I am not a native english speaker so i
don't have a good understanding of the levels of politeness in that
language, but i assure you I did not mean to be disrespectful.
Maybe I didn't read the comments right and I missed the explanations of why
those line were commented out.
I thought Processing looked like an interesting project so I downloaded it.
It didn't work so i thought it was a bug. I checked out the svn version if
the bug was still present, which it was, so i compared different revisions
to see what change cause the bug. After some time i found what i thought
was a solution and wrote about it in the appropriate bugreport. That was
yesterday and it seems my help was appreciated.
Today it seems like it isn't anymore.
I am sorry.