Excessive printing of "an unidentified error occurred".

[RemonNicolai]

Whenever I start an experiment for the first time while running OpenSesame excessive output - "an unidentified error occurred" - is printed in the console. The experiment runs fine, but the printing doesn't stop until I close OpenSesame. It excessively consumes resources, causing me to be unable to browse websites or perform other jobs in e.g. Python.

[smathot]

Hi @RemonNicolai ,

Thanks for reporting this. To narrow the issue down, can you provide some more information?

• What do you see exactly in the console? Please copy-paste the full error message or include a clear screenshot with all relevant information.
• What operating system are you using?
• What version of OpenSesame are you using?
• Does this happen on all backend (General Properties → Run experiment) or only some backends?
• Does this happen for all experiments, including the template, or only a specific one?

— Sebastiaan

[RemonNicolai]

Hi @smathot,

Of course, sorry for not including that immediately.

• 
• Windows 11
• OpenSesame 4.0
• All backends.
• It doesn't happen for the template, unless I add inline scripting.

To be more precise, the printing already happens before the experiment actually starts running.

[smathot]

OpenSesame 4.0

Which version exactly? (4.0.X)? Did you apply all the updates provided by the automatic updater?

unless I add inline scripting.

I assume this is a Python inline_script? Does it matter whether you add any code the script, or is just adding the item sufficient?

[RemonNicolai]

• 4.0.24. All updates are applied.
• Yes, Python inline_script. Just adding the item is sufficient.

[smathot]

4.0.24. All updates are applied.

The latest version is currently 4.0.37. After starting OpenSesame, you will get a notification that updates are available. (This may take a while though, because Anaconda is really slow.) Then you can execute the update script that is offered to you. Can you try this and then let me know whether or not the issue persists?

[RemonNicolai]

Hmm, I see. I did not get the notification until I ran it as an administrator, nonetheless, I could update it just now.

The error does not seem to occur anymore, so that's great! Thank you for your help.