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 in LanguageBundle.read() on startup #4417

Closed
Futuremanzero opened this Issue Apr 20, 2016 · 14 comments

Comments

Projects
None yet
5 participants
@Futuremanzero

Futuremanzero commented Apr 20, 2016

Hello, I just got this error when trying to open 3.0.2 for the first time. Windows 10 64-bit.

error

@Futuremanzero

This comment has been minimized.

Show comment
Hide comment
@Futuremanzero

Futuremanzero Apr 20, 2016

I think I figured out what's happening. If the folder for processing 3.0.2 is on my desktop it will open and work but if I move it (or extract a new copy) into the folder where I organize previous versions of processing then I get this error. For now I'll run it off my desktop, but if anyone knows a solution so that I can move it and it will still work I would greatly appreciate it.

Futuremanzero commented Apr 20, 2016

I think I figured out what's happening. If the folder for processing 3.0.2 is on my desktop it will open and work but if I move it (or extract a new copy) into the folder where I organize previous versions of processing then I get this error. For now I'll run it off my desktop, but if anyone knows a solution so that I can move it and it will still work I would greatly appreciate it.

@Futuremanzero Futuremanzero changed the title from Processing 3.02 Error to Processing 3.0.2 Error Apr 20, 2016

@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Apr 22, 2016

Contributor

Hi, thanks for the report.

Could you please post full file paths where it worked and where it didn't work?

Contributor

JakubValtar commented Apr 22, 2016

Hi, thanks for the report.

Could you please post full file paths where it worked and where it didn't work?

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Apr 22, 2016

Member

That sounds like you're moving just Processing.exe to another location, not the entire folder. Is that the case? You have to keep the entire Processing folder intact, otherwise you'll see errors like this, which is happening because it cannot find its support files.

Member

benfry commented Apr 22, 2016

That sounds like you're moving just Processing.exe to another location, not the entire folder. Is that the case? You have to keep the entire Processing folder intact, otherwise you'll see errors like this, which is happening because it cannot find its support files.

@Futuremanzero

This comment has been minimized.

Show comment
Hide comment
@Futuremanzero

Futuremanzero Apr 24, 2016

Hi all, the original path was:
C:\Users\Owner\Desktop

The problem appeared when I moved the processing-3.0.2 folder and its contents to a folder on the desktop where I've been keeping the folders with prior versions of processing to keep them organized. I tested 2.0 and 3.0b6 and both of those versions seem to work fine after moving them.

I played around with it a bit and I renamed that folder from "Processing + Arduino" to "Processing Arduino" (dropped the plus) and now it seems to be working fine. Not sure if that's what caused it since the other versions didn't seem to have a problem with the folder name, but now its working.

Thanks!

Futuremanzero commented Apr 24, 2016

Hi all, the original path was:
C:\Users\Owner\Desktop

The problem appeared when I moved the processing-3.0.2 folder and its contents to a folder on the desktop where I've been keeping the folders with prior versions of processing to keep them organized. I tested 2.0 and 3.0b6 and both of those versions seem to work fine after moving them.

I played around with it a bit and I renamed that folder from "Processing + Arduino" to "Processing Arduino" (dropped the plus) and now it seems to be working fine. Not sure if that's what caused it since the other versions didn't seem to have a problem with the folder name, but now its working.

Thanks!

JakubValtar added a commit to JakubValtar/processing that referenced this issue Apr 24, 2016

Fix file path decoding
URLDecoder was being used for path decoding, even though it can't handle
RFC2396 encoding. This resulted in plus characters being removed and
possibly other weirdness.

See https://docs.oracle.com/javase/8/docs/api/java/net/URL.html
"The recommended way to manage the encoding and decoding of URLs is to
use URI, and to convert between these two classes using toURI() and
URI.toURL(). The URLEncoder and URLDecoder classes can also be used, but
only for HTML form encoding, which is not the same as the encoding
scheme defined in RFC2396."

Fixes #4417
@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Apr 24, 2016

Contributor

Thanks @Futuremanzero, there was a bug and paths with '+' characters were handled incorrectly. It's fixed in my PR and should be merged soon.

Contributor

JakubValtar commented Apr 24, 2016

Thanks @Futuremanzero, there was a bug and paths with '+' characters were handled incorrectly. It's fixed in my PR and should be merged soon.

@itzikt

This comment has been minimized.

Show comment
Hide comment
@itzikt

itzikt Apr 30, 2016

Hi all !
problem not solved ! - I download today 'processing-3.0.2-windows64' - and the same problem that was describe by 'Futuremanzero' in the top of this issue occurs ! (in my case - I installed under folder named DCC++)

Meanwhile , I found a bypass
To solved the problem - Just validate that the extract of zip file will be done in a folder that** his full path name will not include the sign "+"**

itzikt commented Apr 30, 2016

Hi all !
problem not solved ! - I download today 'processing-3.0.2-windows64' - and the same problem that was describe by 'Futuremanzero' in the top of this issue occurs ! (in my case - I installed under folder named DCC++)

Meanwhile , I found a bypass
To solved the problem - Just validate that the extract of zip file will be done in a folder that** his full path name will not include the sign "+"**

@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Apr 30, 2016

Contributor

Hi @itzikt,

  1. my pull request it not merged yet
  2. it will be fixed in next release (3.0.3 or 3.1)
Contributor

JakubValtar commented Apr 30, 2016

Hi @itzikt,

  1. my pull request it not merged yet
  2. it will be fixed in next release (3.0.3 or 3.1)
@itzikt

This comment has been minimized.

Show comment
Hide comment
@itzikt

itzikt May 1, 2016

Than's
no problem, meanwhile can use the bypass

On Sat, Apr 30, 2016 at 11:43 PM, Jakub Valtar notifications@github.com
wrote:

Hi @itzikt https://github.com/itzikt,

  1. my pull request it not merged yet
  2. it will be fixed in next release (3.0.3 or 3.1)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#4417 (comment)

itzikt commented May 1, 2016

Than's
no problem, meanwhile can use the bypass

On Sat, Apr 30, 2016 at 11:43 PM, Jakub Valtar notifications@github.com
wrote:

Hi @itzikt https://github.com/itzikt,

  1. my pull request it not merged yet
  2. it will be fixed in next release (3.0.3 or 3.1)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#4417 (comment)

@MattGarfield

This comment has been minimized.

Show comment
Hide comment
@MattGarfield

MattGarfield Jul 21, 2016

I've run into this issue with Processing 3.1.1 on a Windows 7 PC on a Domain network with Roaming Profiles. I've seen issue with other software packages having trouble with Roaming Profiles because the file path uses a '$' for redirection. I'm not sure if the '$' is part of the problem here, but since the original issue was related to '+' in the file path, I think this is a good candidate.

I can confirm that Processing runs normally if I move the folder to C;/, which eliminates the profile redirection filepath with the '$'. I happen to be an admin with permission to do this. Most users in my organization would not be able to employ this as a workaround.

This is also a difficult issue to troubleshoot because there is a minority subset of users with Processing 3.1.1 on Windows 7 on a Domain Network with Profile Redirection.

@JakubValtar Can you validate that the fix you employed for the '+' would have also handled '$' in the file path? If not, could you include '$' as a valid filepath character in the next version?

processing error

MattGarfield commented Jul 21, 2016

I've run into this issue with Processing 3.1.1 on a Windows 7 PC on a Domain network with Roaming Profiles. I've seen issue with other software packages having trouble with Roaming Profiles because the file path uses a '$' for redirection. I'm not sure if the '$' is part of the problem here, but since the original issue was related to '+' in the file path, I think this is a good candidate.

I can confirm that Processing runs normally if I move the folder to C;/, which eliminates the profile redirection filepath with the '$'. I happen to be an admin with permission to do this. Most users in my organization would not be able to employ this as a workaround.

This is also a difficult issue to troubleshoot because there is a minority subset of users with Processing 3.1.1 on Windows 7 on a Domain Network with Profile Redirection.

@JakubValtar Can you validate that the fix you employed for the '+' would have also handled '$' in the file path? If not, could you include '$' as a valid filepath character in the next version?

processing error

@itzikt

This comment has been minimized.

Show comment
Hide comment
@itzikt

itzikt Jul 22, 2016

Dear Matt !

your fix is working.

Just finish to check it with variation file path name (including '+' /
'$' / '++' / '++$') and it's work perfect.

Thank's

Itzik

On 21 Jul 2016 22:08, "Matt Garfield" notifications@github.com wrote:

I've run into this issue with Processing 3.1.1 on a Windows 7 PC on a
Domain network with Roaming Profiles. I've seen issue with other software
packages having trouble with Roaming Profiles because the file path uses a
'$' for redirection. I'm not sure if the '$' is part of the problem here,
but since the original issue was related to '+' in the file path, I think
this is a good candidate.

This is also a difficult issue to troubleshoot because there is a
minority small subset of users with Processing 3.1.1 on Windows 7 on a
Domain Network with Profile Redirection.

@JakubValtar Can you validate that the fix you employed for the '+' would
have also handled '$' in the file path?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

itzikt commented Jul 22, 2016

Dear Matt !

your fix is working.

Just finish to check it with variation file path name (including '+' /
'$' / '++' / '++$') and it's work perfect.

Thank's

Itzik

On 21 Jul 2016 22:08, "Matt Garfield" notifications@github.com wrote:

I've run into this issue with Processing 3.1.1 on a Windows 7 PC on a
Domain network with Roaming Profiles. I've seen issue with other software
packages having trouble with Roaming Profiles because the file path uses a
'$' for redirection. I'm not sure if the '$' is part of the problem here,
but since the original issue was related to '+' in the file path, I think
this is a good candidate.

This is also a difficult issue to troubleshoot because there is a
minority small subset of users with Processing 3.1.1 on Windows 7 on a
Domain Network with Profile Redirection.

@JakubValtar Can you validate that the fix you employed for the '+' would
have also handled '$' in the file path?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@JakubValtar

This comment has been minimized.

Show comment
Hide comment
@JakubValtar

JakubValtar Jul 22, 2016

Contributor

I built a small network from my laptops and the problem is caused by running from the network location. It handles $ properly so that's just a red herring. I'll investigate today and prepare a fix since now I can reproduce the issue.

Contributor

JakubValtar commented Jul 22, 2016

I built a small network from my laptops and the problem is caused by running from the network location. It handles $ properly so that's just a red herring. I'll investigate today and prepare a fix since now I can reproduce the issue.

@MattGarfield

This comment has been minimized.

Show comment
Hide comment
@MattGarfield

MattGarfield Jul 22, 2016

Ah, ok- thanks for digging in and identifying the true cause of the issue!

MattGarfield commented Jul 22, 2016

Ah, ok- thanks for digging in and identifying the true cause of the issue!

@benfry benfry changed the title from Processing 3.0.2 Error to NullPointerException in LanguageBundle.read() on startup Jul 28, 2016

@benfry benfry added the windows label Jul 28, 2016

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jul 28, 2016

Member

Fix now included for 3.1.2.

Member

benfry commented Jul 28, 2016

Fix now included for 3.1.2.

@benfry benfry referenced this issue Jul 28, 2016

Closed

Launch error #4568

@MattGarfield

This comment has been minimized.

Show comment
Hide comment
@MattGarfield

MattGarfield Jul 29, 2016

Yesssss! Thank you!

MattGarfield commented Jul 29, 2016

Yesssss! Thank you!

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