New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NullPointerException inside buildCoreModes() when starting 3.0.1 on Windows #4128

Closed
camelbob opened this Issue Nov 10, 2015 · 8 comments

Comments

Projects
None yet
4 participants
@camelbob

camelbob commented Nov 10, 2015

After downloading and unpacking version 3.0.1 I get a window titled "We're off on the wrong foot" Contents of window include, "An error occurred during startup" " java.lang.NullPointerException at processing.app.Base.buildCoreModes(Base.java:357). See attached jpeg.

I am running windows 7 enterprise with service pack 1 on a HP Folio 13 -2000 notebook PC. All recent versions of processing have installed and run ok
wrong foot

@IAmSpring

This comment has been minimized.

Show comment
Hide comment
@IAmSpring

IAmSpring commented Apr 2, 2016

bump

@benfry benfry changed the title from Null pointer exception on startup with 3.0.1 to NullPointerException inside buildCoreModes() when starting 3.0.1 on Windows May 8, 2016

@hx2A

This comment has been minimized.

Show comment
Hide comment
@hx2A

hx2A Jul 10, 2016

I get the same error message on linux with processing 3.1.1. Any suggestions for what to do here?

hx2A commented Jul 10, 2016

I get the same error message on linux with processing 3.1.1. Any suggestions for what to do here?

@benfry benfry removed the windows label Jul 29, 2016

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jul 29, 2016

Member

I have no idea; I've never seen this and can't find a way to reproduce it.

The error seems to be happening because it can't find the folder that contains "Java Mode". Is there something strange about how the files have been unpacked from the archive? Have you messed with the Processing folder itself somehow?

Member

benfry commented Jul 29, 2016

I have no idea; I've never seen this and can't find a way to reproduce it.

The error seems to be happening because it can't find the folder that contains "Java Mode". Is there something strange about how the files have been unpacked from the archive? Have you messed with the Processing folder itself somehow?

@hx2A

This comment has been minimized.

Show comment
Hide comment
@hx2A

hx2A Aug 3, 2016

Thank you! Your reply stimulated the insight I needed to fix this. It only took a few minutes after I sat down in front of my computer.

The problem was my Java CLASSPATH. For reasons related to a project I did a few years ago, I had a set of Processing jar files (probably 2.2.1) in a directory that was always in my CLASSPATH. I realize now that this is not a good idea but it made sense at the time.

When the Processing startup script runs it adds its own files and directories to the end of the CLASSPATH before launching the application. Since my other set of Processing jar files were ahead of the correct jar files, the JRE would load classes from those jars first. Not surprisingly, that is bad for Processing.

To fix it, I simply had to simply remove my addition to my CLASSPATH. It worked right away after that.

hx2A commented Aug 3, 2016

Thank you! Your reply stimulated the insight I needed to fix this. It only took a few minutes after I sat down in front of my computer.

The problem was my Java CLASSPATH. For reasons related to a project I did a few years ago, I had a set of Processing jar files (probably 2.2.1) in a directory that was always in my CLASSPATH. I realize now that this is not a good idea but it made sense at the time.

When the Processing startup script runs it adds its own files and directories to the end of the CLASSPATH before launching the application. Since my other set of Processing jar files were ahead of the correct jar files, the JRE would load classes from those jars first. Not surprisingly, that is bad for Processing.

To fix it, I simply had to simply remove my addition to my CLASSPATH. It worked right away after that.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Aug 4, 2016

Member

Agh; that's an exceptionally bad idea. How were you setting the CLASSPATH? Environment variable? It shouldn't be using the machine's CLASSPATH at all so I need to figure out how to avoid that.

Member

benfry commented Aug 4, 2016

Agh; that's an exceptionally bad idea. How were you setting the CLASSPATH? Environment variable? It shouldn't be using the machine's CLASSPATH at all so I need to figure out how to avoid that.

@hx2A

This comment has been minimized.

Show comment
Hide comment
@hx2A

hx2A Aug 5, 2016

Agh; that's an exceptionally bad idea.

I agree! I was young and foolish.

How were you setting the CLASSPATH? Environment variable?

I was setting it with an export CLASSPATH=... statement in my .bashrc file. I have a Linux (Ubuntu) box.

It shouldn't be using the machine's CLASSPATH at all so I need to figure out how to avoid that.

True. If there is anything I can do to help you do figure out how to do that, please ask.

hx2A commented Aug 5, 2016

Agh; that's an exceptionally bad idea.

I agree! I was young and foolish.

How were you setting the CLASSPATH? Environment variable?

I was setting it with an export CLASSPATH=... statement in my .bashrc file. I have a Linux (Ubuntu) box.

It shouldn't be using the machine's CLASSPATH at all so I need to figure out how to avoid that.

True. If there is anything I can do to help you do figure out how to do that, please ask.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Aug 6, 2016

Member

Added workaround for Processing 3.2, see #4608

But let me know if that doesn't fix it; it's possible that CLASSPATH is handled differently.

Member

benfry commented Aug 6, 2016

Added workaround for Processing 3.2, see #4608

But let me know if that doesn't fix it; it's possible that CLASSPATH is handled differently.

@benfry benfry closed this Aug 6, 2016

@hx2A

This comment has been minimized.

Show comment
Hide comment
@hx2A

hx2A Aug 7, 2016

Nice. Happy to contribute to progress.

hx2A commented Aug 7, 2016

Nice. Happy to contribute to progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment