Can't run my program when console is overloaded. about processing HOT 7 CLOSED

Unfortunately there's not much more we can do here. There are already some things in the code that try to prevent the app from locking up in these cases. But at the end of the day, you're writing a program, and you ask the computer to do too much, then you can also make it crash.

from processing.

@benfry If stdout and stderr messages are mixed together, there is a bug in Processing in its multithreading handling this. I tried to fix this here with a lock, but that doesn't seem like a good way to do it (i know near nothing about multithreading). Thoughts?

(Processing 3 also seems to just lock up (no errors, no CPU usage) on lots of regular printing, but I can't reproduce this in processing 4)

from processing.

Not sure; I'm not aware of any stdout/stderr deadlock in that code but it's certainly a possibility. Unfortunately I can't make much sense of that commit because it's 23 files.

from processing.

I linked to the start of the important changes in the app/src/processing/app/ui/EditorConsole.java file, but the links can be buggy; link to final file. (I had to squash the files when the processing 4 history was rewritten to remove large files; probably could've avoided doing that, but didn't bother). for (int i = 0; i < 10000; i++) { println("out"); System.err.println("err"); } quickly results in some java.util.EmptyStackExceptions being thrown and running being broken.

from processing.

Moving that here: benfry/processing4#338

from processing.

@EinsMalte Found some related issues for this which are fixed here: benfry/processing4#338, so thanks for bringing it to my attention. Hopefully it'll help with the case that you ran into as well.

from processing.

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.

from processing.