# Processing IDE 4.4.4 does not show line in error

**URL:** <https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915>\
**Category:** Processing\
**Created:** [August 12, 2025, 5:38pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915 "2025-08-12T17:38:07Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhole](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@rhole](https://discourse.processing.org/u/rhole)\
**Post date:** [August 12, 2025, 5:38pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/1 "2025-08-12T17:38:07Z")

</div>

```auto
void setup(){
  println("arrived at setup");
  // force a divide check to illustrate how errors are displayed
  int x= 0;
  int y= 2/x;
  x=y;
}

```

```auto

void setup(){
println(“arrived at setup”);
// force a divide check to illustrate how errors are displayed
int x= 0;
int y= 2/x;
x=y;
}

```

The code above is a short sample to illustrate. The real code has 1000+ lines and finding where the error happened is quite a chore. I may have to revert to IDE 3.5.3 just to get that help.

I have upgraded from the 3.5.3 IDE to 4.4.4. Run-time errors are not indicating the code line is question making debug a horrendous battle! I am working in Java mode and have reinstalled the IDE, same problem Do I have a setting wrong? Or any suggestions. Thanks

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/c/d/cd68909df2e158fb3e8140c0aa8a50f69ceac5b6.png)

---

<div class="post-metadata">

**Author:** ![bonner45](https://avatars.discourse-cdn.com/v4/letter/b/53a042/32.png) [@bonner45](https://discourse.processing.org/u/bonner45)\
**Post date:** [August 12, 2025, 7:14pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/3 "2025-08-12T19:14:20Z")

</div>

Please post the full code. 😎

---

<div class="post-metadata">

**Author:** ![rhole](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@rhole](https://discourse.processing.org/u/rhole)\
**Post date:** [August 12, 2025, 7:37pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/4 "2025-08-12T19:37:13Z")

</div>

Too many lines to post effectively. I will work up a short example. In the IDE 3.5.3 the editor window to switch to show where the error was detected and highlight that line. 4.4.4 just gives an error message with no clue where it occurred. I will amend my post soon.

---

<div class="post-metadata">

**Author:** ![bonner45](https://avatars.discourse-cdn.com/v4/letter/b/53a042/32.png) [@bonner45](https://discourse.processing.org/u/bonner45)\
**Post date:** [August 12, 2025, 10:06pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/5 "2025-08-12T22:06:48Z")

</div>

I think it’s being worked on.😎

> <https://github.com/benfry/processing4/issues/741>
>
> \# Processing Friendly Errors
> We are building out friendly error message rewriti…ng by extending the \[PreprocessIssueMessageSimplifier\](https://github.com/processing/processing4/blob/main/java/src/processing/mode/java/preproc/PreprocessIssueMessageSimplifier.java). To determine which errors to support, we worked with \[Raphaël\](https://github.com/SableRaf) and \[Sam\](https://github.com/sampottinger) to run a community survey.
> 
> \## Motivations
> The results of the survey showed that although the error messages are usable, with an average clarity rating of 3.32 out of 5 there is room for improvement. The key elements that respondents identified as crucial for understanding error messages include the name and type of the error, specifics about what broke in the code, traceback to the specific line of the error, expected versus found outcomes, resources for contextualization and guidance, and possible solutions. Enhancing error messages based on the insights of the survey would greatly benefit the Processing user experience for beginners and advanced users alike. We hope to foster better understanding and more efficient problem-solving.
> 
> \## Currently Simplified Errors to Improve On
>  
> | Strategy | Current Error Output | Acknowledged In Survey | URL |
> |:------------:|----------------------|:--:|:-----------:|
> | InvalidIdentifierStrategy | Bad identifier? Did you forget a variable or start an identifier with digits near ‘statement’ | ✅ |\[Variables\](https://docs.oracle.com/javase/tutorial/java/nutsandbolts/variables.html) \<br\> OR \<br\> \[Variable Examples\](https://processing.org/examples/variables.html), \[Identifiers\](https://docs.oracle.com/cd/E19798-01/821-1841/bnbuk/index.html),\<br\>\[Keywords\](https://docs.oracle.com/javase/tutorial/java/nutsandbolts/\_keywords.html)\<br\> & \<br\>\[Statements\](https://processing.org/examples/statementscomments.html) |
> | MismatchedInputSimplifierStrategy | Missing operator, semicolon, or ‘}’ near ‘statement’ | ✅ | \[Operators\](https://docs.oracle.com/javase/tutorial/java/nutsandbolts/operators.html),\<br\> \[Operators Example\](https://processing.org/examples/logicaloperators.html),\<br\> \[Semicolons\](https://processing.org/reference/semicolon.html),\<br\>\[Curly Braces\](https://processing.org/reference/curlybraces.html)\<br\>& \<br\> \[Statements\](https://processing.org/examples/statementscomments.html)|
> | InvalidAssignmentStrategy | Possible error on variable assignment near ‘statement’ | ✅ | \[Variables\](https://docs.oracle.com/javase/tutorial/java/nutsandbolts/variables.html) \<br\> OR \<br\> \[Variable Examples\](https://processing.org/examples/variables.html),\<br\>\[Assignment Operator\](https://processing.org/reference/assign.html)\<br\>&\<br\>\[Statements\](https://processing.org/examples/statementscomments.html)|
> | VariableDeclarationMissingTypeStrategy | Missing name or ; or type near ‘statement’ | ✅ | \[Variables\](https://docs.oracle.com/javase/tutorial/java/nutsandbolts/variables.html) \<br\> OR \<br\> \[Variable Examples\](https://processing.org/examples/variables.html),\<br\>\[Semicolons\](https://processing.org/reference/semicolon.html), \<br\>\[Identifiers\](https://docs.oracle.com/cd/E19798-01/821-1841/bnbuk/index.html)\<br\> & \<br\> \[Statements\](https://processing.org/examples/statementscomments.html)|
> | MissingCurlyAtStartSimplifierStrategy | Missing left curly bracket “{” | ✅ | \[Curly Braces\](https://processing.org/reference/curlybraces.html) |
> | MissingCurlyAtSemicolonSimplifierStrategy | Missing right curly bracket “}” | ✅ | \[Curly Braces\](https://processing.org/reference/curlybraces.html) |
> | UnbalancedChevStrategy | Missing '\<' OR Missing '\>' | ✅ | \[Generics\](https://docs.oracle.com/javase/tutorial/extra/generics/simple.html),\<br\>\[Generic Methods\](https://docs.oracle.com/javase/tutorial/extra/generics/methods.html)\<br\>&\<br\>\[Generics & Subtyping\](https://docs.oracle.com/javase/tutorial/extra/generics/subtype.html) |
> | InvalidGenericDefinitionStrategy | Possibly missing type in generic near ‘statement’ | ❌ | \[Generics\](https://docs.oracle.com/javase/tutorial/extra/generics/simple.html),\<br\>\[Generic Methods\](https://docs.oracle.com/javase/tutorial/extra/generics/methods.html),\<br\>\[Statements\](https://processing.org/examples/statementscomments.html) \<br\>&\<br\>\[Generics & Subtyping\](https://docs.oracle.com/javase/tutorial/extra/generics/subtype.html) |
> | MissingIdentifierSimplifierStrategy | Missing name or ; near ‘statement’ | ✅ | \[Identifiers\](https://docs.oracle.com/cd/E19798-01/821-1841/bnbuk/index.html) \<br\>&\<br\>\[Statements\](https://processing.org/examples/statementscomments.html) |
> | KnownMissingSimplifierStrategy | Missing “statement” | ❌ | \[Statements\](https://processing.org/examples/statementscomments.html) |
> | ExtraneousInputSimplifierStrategy | ArithmeticException statement or extra code near ‘statement’ | ❌ | \[Arithmetic Exceptions\](https://docs.oracle.com/javase/8/docs/api/?java/lang/ArithmeticException.html),\<br\>\[Operator Precedence\](https://processing.org/examples/operatorprecedence.html)\<br\>&\<br\>\[Statements\](https://processing.org/examples/statementscomments.html) |
> | MissingClassNameStrategy | Missing name or ; near ‘statement’ | ❌ |\[Classes\](https://processing.org/reference/class.html) ,\<br\>\[Identifiers\](https://docs.oracle.com/cd/E19798-01/821-1841/bnbuk/index.html),\<br\>\[Semicolons\](https://processing.org/reference/semicolon.html)\<br\>&\<br\>\[Statements\](https://processing.org/examples/statementscomments.html)|
> | MethodMissingNameStrategy | Missing name or ; near ‘statement’ | ❌ | \[Methods\](https://docs.oracle.com/javase/tutorial/java/javaOO/methods.html),\<br\> \[Identifiers\](https://docs.oracle.com/cd/E19798-01/821-1841/bnbuk/index.html),\<br\>\[Semicolons\](https://processing.org/reference/semicolon.html)\<br\>&\<br\>\[Statements\](https://processing.org/examples/statementscomments.html) |
> | ErrorOnParameterStrategy | Error on parameter or method declaration near ‘statement’ | ❌ |\[Parameters\](https://docs.oracle.com/javase/tutorial/java/javaOO/arguments.html),\<br\>\[Methods\](https://docs.oracle.com/javase/tutorial/java/javaOO/methods.html)\<br\>&\<br\>\[Statements\](https://processing.org/examples/statementscomments.html) |
> | MissingSingleQuoteStrategy | Missing “'” | ❌ | \[Chars\](https://processing.org/reference/char.html) |
> | MissingDoubleQuoteStrategy | Missing “"” | ❌ | \[Strings\](https://processing.org/reference/String.html) |
> | UnbalancedCurlyStrategy | Missing "{" OR Missing "}" | ✅ | \[Curly Braces\](https://processing.org/reference/curlybraces.html) |
> | UnbalancedParenStrategy | Missing "(" OR Missing ")" | ✅ | \[Parentheses\](https://processing.org/reference/parentheses.html) |
> | DefaultMessageSimplifier | \<ul\>\<li\>Error\</li\>\<li\>Error on variable assignment near 'statement'\</li\>\<li\>Identifier cannot start with digits near 'statement'\</li\>\<li\>Error on parameter or method declaration near 'statement'\</li\>\<li\>Unexpected extra code near 'statement'\</li\>\<li\>Missing operator or semicolon near 'statement'\</li\>\<li\>Missing name near 'statement'\</li\>\<li\>Missing name or type near 'statement'\</li\>\<li\>Missing 'statement'\</li\>\<li\>Missing '}'\</li\>\<li\>Missing '{'\</li\>\</ul\> | n/a | TBD |    
>       
> \## Errors to Add Strategies For
> 
> |Priority|Error|
> |------|---------|
> |First| \<ul\>\<li\>ArrayIndexOutOfBoundException\</li\>\<li\>NullPointerException\</li\>\<li\>UnsupportedOperationException\</li\>\<li\>NumberFormatException\</li\>\<li\>StackOverflowError\</li\>\<li\>IndexOutOfBoundsException\</li\>\<li\>StringIndexOutOfBoundsException\</li\> \</ul\>|
> |Secondary|\<ul\>\<li\>ClassCastException\</li\>\<li\>IllegalThreadStateException\</li\>\<li\>IllegalStateException\</li\>\<li\>ArrayStoreException\</li\>\<li\>NoSuchMethodError\</li\>\</ul\>|
> |TBD|\<ul\>\<li\>FileNotFoundException\</li\>\<li\>IOException\</li\>\<li\>ConcurrentModificationException\</li\>\<li\>EnumConstantNotPresentException\</li\>\</ul\>|
> 
> \## Unsupported Errors
> The following will still operate as usual without rewriting / error simplification.
> 
> \- Variable is named after keyword
> \- GLSL/Shader errors
> \- Compatibility issues with Android extensions
> \- Library errors
> \- Python errors
> \- p5.js errors
> 
> \## Error Message Template
> 
> |Optional?| Feature |
> |:----------------------------:|----------------------------|
> |❌ |Processing found an \[error type\](optional) error at \[error line\](link moves cursor to line number)!|
> |❌ |\[error context\]|
> |✅ |\[reminder / additional context\] OR We expected \[expectation\] but found \[x\]!|
> |✅ |We suggest \[hint\]!|
> |✅ |+ More Info on:\<br\>-\[additional resources\]
> |❌ |▶Click to See Original Error! \[Toggles Original Error\] \*|
> 
> \\\* The toggle to see the original error will be added at some point but likely will not be in the first version of the improved error messages as it may be difficult to implement.
> 
> \## Example 1: Array Index Out of Bound Exception
> 
> \> 🔵 Processing says: Oops! It looks like you're trying to look at an item in your 'numbers' \[array\](https://processing.org/reference/Array.html) that doesn't exist. (On line 3 in sketch\_230707c.pde)\<br\>\<br\>Remember, counting in Processing starts from 0, not 1. This means your 'numbers' \[array\](https://processing.org/reference/Array.html), which has 3 items, has positions labelled from 0 to 2. If you're trying to find an item at position 3 and above (or below 0), it won't work because there's no item there!\<br\>To fix this, make sure you're looking at positions that exist in your 'numbers' \[array\](https://processing.org/reference/Array.html), that is, positions from 0 to 2.\<br\>\<br\>For more:https://processing.org/examples/array.html
> 
> 
> \## Example 2: Invalid Identifier
> \>🔵 Processing says: Uh-oh! There's an issue with a "bad identifier" in your code. Specifically, the issue is with 'int 9'. (On line 48 in sketch\_230710a.pde)\<br\>\<br\>In Processing, identifiers (like variable names, function names, etc.) can not start with a number and should only include letters, numbers, or underscores. Therefore, '9' is not a valid name.\<br\>\<br\>Here's a quick fix: Try renaming your identifier so that it starts with a letter, dollar sign($) or an underscore(\_). Make sure the name you choose is not a reserved keyword like "setup" or "width".\<br\>
> For more:\<br\>https://processing.org/examples/variables.html\<br\>https://processing.org/examples/functions.html
> 
> 
> \## Incorporating Additional Resources Approach
> \- When directing the users to external resources the goal is to direct them towards Processing resources when possible and towards official Java documentation as a last resort as it is significantly less user friendly than Processing resources.
> \- To not overwhelm the user with links to external resources we will link them inline with the error message if the keyword is conveniently in the message itself otherwise they will be in the "For more:" section at the bottom. The "For more:" section will also contain examples of the concepts when applicable.

---

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [August 13, 2025, 2:18am UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/6 "2025-08-13T02:18:49Z")

</div>

Hello @rhole,

It works in Processing 4.3.4 in Windows 10:

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/0/d/0d52585e6fda9a3dcd2bd1d6babff70d68a6dbca.png)

Related:

> [@Stack Trace for Exceptions](https://discourse.processing.org/t/stack-trace-for-exceptions/46569):
>
> How to get a stack-trace if the program throws an exception (or any information pointing to the position in the program from where the exception was thrown?) Example (a typical beginner’s mistake): PVector [] vs = new PVector [10]; for (int i=0;i\<vs.length;++i) vs[i].set(0,0); When running this in processing, all it does is displaying a red NullPointerException message. I cannot see any way to find out where in the program this was thrown. (Ideally, I would like to see a stack trace). If…

> <https://github.com/processing/processing4/issues/1153>
>
> \### Most appropriate sub-area of Processing 4?
> 
> PDE
> 
> \### Processing version
> 
> 4.4….4
> 
> \### Operating system
> 
> Ubuntu 24.04, Windows 10
> 
> \### Bug description
> 
> The location of an exception (e.g. NullPointerException) is not highlighted, nor is a stack trace printed. The only information printed is a red NullPointerException message at the bottom. There is no obvious way how to find out where this was thrown.
> 
> This seems to be a regression to earlier 3.x versions, where the line of the thrower would be at least highlighted. 
> 
> 
> 
> \### Steps to reproduce this
> 
> "1. open the below snippet in PDE
> 
> 2. run the snippet
> 
> 3. observe that the error message (NullPointerException) is not linked to any position in the code, nor is any position in the code highlighted, nor is a stack-trace or similar printed anywhere"
> 
> 
> \### snippet
> 
> \`\`\`
> PVector \[\] vs = new PVector\[10\];
> for (int i=0;i\<vs.length;++i)
> vs\[i\].set(0,0); // \<-- this position should be contained in the error message
> 
> \`\`\`
> 
> 
> \### Additional context
> 
> real showstopper when trying to debug any bigger program in PDE!
> 
> \### Would you like to work on the issue?
> 
> No, I’m just reporting the issue

This (from github issue) highlights error in Processing 4.3.4:

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/9/f/9f5c3fb753aa92f7ea795016ace2bd95d91f130a.png)

`:)`

---

<div class="post-metadata">

**Author:** ![svan](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@svan](https://discourse.processing.org/u/svan)\
**Post date:** [August 13, 2025, 2:21am UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/7 "2025-08-13T02:21:41Z")

</div>

It’s a known issue with Processing 4.4.4. You might consider dropping back to 4.3.x.

---

<div class="post-metadata">

**Author:** ![rhole](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@rhole](https://discourse.processing.org/u/rhole)\
**Post date:** [August 13, 2025, 6:20am UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/9 "2025-08-13T06:20:59Z")

</div>

Thanks, I installed 4.3.4 and it handles the errors as expected. Whew! What a relief!!!

---

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [August 14, 2025, 12:35pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/10 "2025-08-14T12:35:18Z")

</div>

> [@svan](#):
>
> It’s a known issue with Processing 4.4.4. You might consider dropping back to 4.3.x.

> [@Chrisir](#):
>
> Annoying
> 
> They really should take back the download

Processing 4.0 was a major leap forward from Processing 3.5.4 and certainly had its challenges along the way.

Processing 4.0:

> **[Release Processing 4.0 alpha 1 · processing/processing4](https://github.com/processing/processing4/releases/tag/processing-1270-4.0a1)**
>
> Revision 1270 - 18 January 2019
> This is a massive update! With the help of Sam Pottinger, we're working to get Processing to run with Java 11. This will give us a more stable platform for the next ...

Lots of other changes in between from 4.0 to 4.3.

Processing 4.4 is another step forward from 4.3 and will certainly also have challenges:

> **[Release Processing 4.4.0 · processing/processing4](https://github.com/processing/processing4/releases/tag/processing-1300-4.4.0)**
>
> Happy Pi Day!
> Today we are finally releasing Processing 4.4.0!
> There are a few noticeable changes for users. Processing now installs more seamlessly across platforms. Windows users get a new .msi i...

> Most of the work happened behind the scenes, including various quality-of-life improvements for developers working on the codebase. Key updates include **migrating the build system from Ant to Gradle** and **beginning the transition from Swing to Jetpack Compose Multiplatform**. This is part of a global effort to modernize the project’s infrastructure to support future developments, and make it easier for more people to get involved.

“The only constant in life is change.” - Heraclitus

This applies to software as well!  
We are all living with this reality and the challenges of updates… it is not just Processing.

Perusing the releases shows all the progress that has been made!  
_[Releases · processing/processing4 · GitHub](https://github.com/processing/processing4/releases)_

It would like to see the _ **issues** _ communicated to users in a simple transparent way.  
I don’t have a simple solution for this.  
_ **The Processing Community Forum and GitHub may not be used by everyone and if they do come here we could direct them to the issues resources as a first step.** _

A _ **simplified list** _ to _ **current issues** _ could be linked:

- On the main Processing website where it is easy to find.
- It should be _one stop shopping_, easy to find and maintained and up to date.
- Links to Processing Community Forum and GitHub if further support is needed.
- Alongside the download would a logical choice:  
[Download Processing / Processing.org](https://processing.org/download)
- Processing Community Forum may want to have a pinned post linking to it.
- GitHub releases could link to it.

I am experienced and that simplifies the process of finding answers and solutions.  
Finding help for Processing can be a challenge.  
The **Processing Community Forum** and **GitHub** are full of useful information, but they also have a lot of different threads, versions, and operating systems to sort through.  
It’s easy to get lost or overwhelmed when you’re just trying to find a simple solution.  
New and inexperienced users will certainly struggle.  
I can also struggle at times!  
My preference is always a link to a resource than to answer questions; in forum posts that I both read and post.  
_“Teach someone to fish instead of giving them the fish”_ (short version) empowers users.

All that being said… I would like to see a future update address the reporting of errors sooner than later.  
I too find myself using Processing 4.3.4 for bug reporting alongside Processing 4.4.4.  
This is an example of one of the _ **issues** _ that could be listed with the Processing 4.4.x current releases.

@ProcessingOrg  
Thank you to the Processing team for all the work done in keeping Processing up to date!

`:)`

---

<div class="post-metadata">

**Author:** ![sableraph](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/sableraph/32/251_2.png) [@sableraph](https://discourse.processing.org/u/sableraph)\
**Post date:** [August 14, 2025, 12:55pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/11 "2025-08-14T12:55:04Z")

</div>

Thanks @glv for sharing these links and for your suggestions 💙

Processing is free and open-source, developed and maintained by two people, together with occasional volunteers, and with support from the Processing Foundation. We do our best to share updates as they happen, but we don’t always manage to cover every channel in real time.

As @glv rightly pointed out, Processing is currently undergoing a major technical upgrade behind the scenes and, while we work hard to keep everything functioning as expected, some bugs can slip through.

I know how frustrating it can be when something that used to work no longer does, especially when it slows down debugging your sketches. This particular issue will require bigger changes under the hood before it can be fixed, but we’re on it!

If you’d like to see more about the recent and ongoing work on Processing, these links are a good starting point:

- [Changes in 4.3.1](https://github.com/processing/processing4/wiki/Announcing-Processing-4.3.1)
- [Changes in 4.4](https://github.com/processing/processing4/wiki/Changes-in-4.4)
- Our [Processing talk at Libre Graphics Meeting 2025](https://youtu.be/ngQwedwFyOY?si=c2uRvM9J9B9ZWPBH)

We also welcome contributions from anyone interested in helping improve Processing! If you’d like to work on bug fixes or other improvements, we’re happy to help you [get started contributing](https://github.com/processing/processing4/blob/main/CONTRIBUTING.md).

And yes, we have some exciting things in the works that we’ll be sharing soon!

---

<div class="post-metadata">

**Author:** ![GoToLoop](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/gotoloop/32/86_2.png) [@GoToLoop](https://discourse.processing.org/u/GoToLoop)\
**Post date:** [August 14, 2025, 5:07pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/12 "2025-08-14T17:07:01Z")

</div>

In my experience w/ Processing’s major version transitioning is to stick w/ latest previous major version for more than 1 or more years!

IMO, Processing is too eager to present new major versions as stable, while it still has beta and even alpha issues.

It has been true from Processing 1.x.x to 2.x.x, and to 3.x.x; and now to 4.x.x.

BtW, I’m still using latest legacy 3.5.4 version. Here’s a link to major stable version releases:

> **[Releases](https://processing.org/releases/)**

---

<div class="post-metadata">

**Author:** ![svan](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@svan](https://discourse.processing.org/u/svan)\
**Post date:** [August 14, 2025, 8:08pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/13 "2025-08-14T20:08:00Z")

</div>

If you revert to an older version you will be repeatedly asked to update; here’s how to stop the update dialog:

Set `update.check` to **false** in Preferences:

 ![prefs](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/4/6/460e957ae8f74a073b8e5ec4dd8e169742fde03b.png)

**Alternate method:**  
Make sure this box in the `Preferences dialog` is unchecked:  
 ![updt](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/1/8/18beeb1ae8328b2e4bc490847314bdcc6582b583.png)

---

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [August 15, 2025, 4:06pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/14 "2025-08-15T16:06:58Z")

</div>

> [@svan](#):
>
> Set `update.check` to **false** in Preferences:

Some additional related references for the community:

[https://processing.org](https://processing.org) \> Documentation \> Environment \> Preferences section. Does not have all the details!

[Processing Foundation · GitHub](https://github.com/processing) \> processing4 \> Wiki \> Preferences \> The full list of options is in there!

Have fun!

`:)`

---

<div class="post-metadata">

**Author:** ![Chrisir](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/chrisir/32/45_2.png) [@Chrisir](https://discourse.processing.org/u/Chrisir)\
**Post date:** [August 16, 2025, 5:37am UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/15 "2025-08-16T05:37:06Z")

</div>

Downloaded 4.4.6 now and the issue is not really better.

It doesnt jump to right tab nor scroll

---

<div class="post-metadata">

**Author:** ![EricRogerGarcia](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/ericrogergarcia/32/21029_2.png) [@EricRogerGarcia](https://discourse.processing.org/u/EricRogerGarcia)\
**Post date:** [August 16, 2025, 6:11am UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/16 "2025-08-16T06:11:24Z")

</div>

It’s true but if we don’t use the latest version, we won’t be able to discover all the bugs and escalate them to the programmers…

---

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [August 16, 2025, 3:17pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/17 "2025-08-16T15:17:34Z")

</div>

That is true! I have shared what I learned with the Processing team.

There are exceptions and I am able create custom environments for them:

> [@Can I install Processing 4.4.4 on local drive?](https://discourse.processing.org/t/can-i-install-processing-4-4-4-on-local-drive/46917/4):
>
> \*\* Advanced topics and not for typical installs \*\* These are advanced topics. You should know what you are doing and be able to keep track of your custom working environments. I always do a manual install and rename the folder: A separate preferences.txt for each environment can be created (if desired) and there are instructions here: The .msi installer on Windows does the following: [Android mode no longer works in Processing 4.4.1 · Issue #777 · processing/processing-android ·…](https://github.com/processing/processing-android/issues/777)

I have a few old libraries that only work with older versions of Processing.

`:)`

---

<div class="post-metadata">

**Author:** ![joshg](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/joshg/32/20226_2.png) [@joshg](https://discourse.processing.org/u/joshg)\
**Post date:** [August 17, 2025, 6:26am UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/18 "2025-08-17T06:26:02Z")

</div>

I’ve been working on this and the fix is in the pipeline. PR is submitted and has 1 of 2 approvals. It’s not in 4.4.6 but should be in the next release.

(edit: [No stack trace or thrower position highlighting on exception · Issue #1153 · processing/processing4 · GitHub](https://github.com/processing/processing4/issues/1153) and [Refactoring `SketchException` to be available outside of `app` by joshgiesbrecht · Pull Request #1196 · processing/processing4 · GitHub](https://github.com/processing/processing4/pull/1196) if you want to follow along )

---

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [August 17, 2025, 3:26pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/19 "2025-08-17T15:26:12Z")

</div>

> [@joshg](#):
>
> I’ve been working on this and the fix is in the pipeline.

Thank you!  
I skimmed through all the issues and see the challenges!

Feedback:

_[No stack trace or thrower position highlighting on exception · Issue #1153 · processing/processing4 · GitHub](https://github.com/processing/processing4/issues/1153)_

states:

> It has probably something to do with the integrated JDK within Processing. I suspect that the error reporting probably looking in the wrong place for now.

Something similar here:  
_[Android Programming for Beginners - #16 by glv](https://discourse.processing.org/t/android-programming-for-beginners/46813/16)_

`:)`

---

<div class="post-metadata">

**Author:** ![joshg](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/joshg/32/20226_2.png) [@joshg](https://discourse.processing.org/u/joshg)\
**Post date:** [August 17, 2025, 5:07pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/20 "2025-08-17T17:07:56Z")

</div>

In this case it was due to a custom Exception class being duplicated to help decouple app and backend specific code. The move had left two versions of the class kicking around to keep things from breaking, but then when the app handled an error it wasn’t recognizing the custom Exception type correctly.

It’s been moved in a tidier way now. 😅 All the code in this codebase uses the new one only, and a deprecated-but-functional adapter version is in the old spot while non-java modes move over to the change.

---

<div class="post-metadata">

**Author:** ![rhole](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@rhole](https://discourse.processing.org/u/rhole)\
**Post date:** [August 18, 2025, 3:46pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/21 "2025-08-18T15:46:51Z")

</div>

You can also do it from the IDE. File\>Preferences\>Allow Update Checking (uncheck it)

---

<div class="post-metadata">

**Author:** ![svan](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@svan](https://discourse.processing.org/u/svan)\
**Post date:** [August 18, 2025, 4:31pm UTC](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915/22 "2025-08-18T16:31:28Z")

</div>

> [@rhole](#):
>
> You can also do it from the IDE

Correct; I later discovered that and it’s easier than trying to locate the Preferences file. I edited my post to reflect this.

[Next page](https://discourse.processing.org/t/processing-ide-4-4-4-does-not-show-line-in-error/46915.md?page=2)