Demos run perfectly fine, but PsychoPy won't let me save or run an experiment with one text element!

Builder
1

If this template helps then use it. If not then just delete and start from scratch.

OS (e.g. Win10): Mac OS 10.15
PsychoPy version (e.g. 1.84.x): 3.2.3
Standard Standalone? (y/n) If not then what?:y
What are you trying to achieve?: Making any experiment run

What did you try to make it work?: I tried the demos out which worked, but whenever I try to run my own work, PsychoPy crashes.

What specifically went wrong when you tried that?: The application force closes and goes back to the desktop.
Include pasted full error message if possible.

rocess: PsychoPy3 [10017]
Path: /Applications/PsychoPy3.app/Contents/MacOS/PsychoPy3
Identifier: org.psychopy.PsychoPy3
Version: 3.2.4 (0.0.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: PsychoPy3 [10017]
User ID: 501

Date/Time: 2020-03-12 23:29:20.679 -0400
OS Version: Mac OS X 10.15 (19A487l)
Report Version: 12
Anonymous UUID: 4ED128CF-19DF-65DE-DB83-E28D256938F0

Sleep/Wake UUID: 6FA2F9BC-768F-493D-8EDA-6454B1420B86

Time Awake Since Boot: 450000 seconds
Time Since Wake: 11000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 PTB mainthread Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
Performing @selector(clickedAction:) from sender wxNSMenuItem 0x600002949810
abort() called
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.

Thread 0 Crashed:: PTB mainthread Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff65e5e5be __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff65f1b738 pthread_kill + 203
2 libsystem_c.dylib 0x00007fff65de6a5c abort + 120
3 org.python.python 0x0000000100426551 Py_FatalError + 65
4 org.python.python 0x00000001004293ec PyGILState_Release + 108
5 _core.cpython-36m-darwin.so 0x000000010da05bf0

2

I am experiencing this same error (or a very similar one) now with PsychoPy v 2021.2.3
Demos work, even ones with text but my current experiment fails after the setup routines (which import some csv files, set some variables, etc). I get output is similar to the problem described in the above post. This is an experiment that I ran in April without such problems.

Application Specific Information:
abort() called
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.

… with libsystem_kernel.dylib, libsystem_pthread.dylib, etc. and then a lot of python-related stuff in the queue. I checked my python --version; haven’t upgraded it since writing this experiment, and it lists Python 3.7.6.

In case it was a mac-update problem, I tried some solutions recommended here, including downgrading to 2021.1.4 (the version I originally used to build my experiment), deleting old psychopy versions before installing new ones, and undoing and redoing permissions for input monitoring, none of which changes the behavior.

In the runner, I also get this message when loading in my experiment (only when using v2021.2.3):

Alert 4405: Editable textbox component freeRecallResp and keyboard component endRecallKeypress in the same routine may compete for keypresses
For more info see https://docs.psychopy.org/alerts/4405.htmlAlert 4405: Editable textbox component freeRecallResp and keyboard component endRecallKeypress in the same routine may compete for keypresses

… but the page indicated by the link (Alert 4405) doesn’t seem to exist anymore.

OS (e.g. Win10): Mac OS 10.15.7 Catalina
PsychoPy version : 2021.2.3 (also tried 2021.1.4, same issue)
Standard Standalone? (y/n) y

3

Update: I tried building a new experiment from the ground up. Things went well for a little while, and then I got the same dylib error. After some testing, it seems that for me, it was the addition of a .png image that was causing this crash-- when I disable that component, it runs better. I don’t need it so I just removed it; but I can see how this would cause problems. Anyway, hope this helps someone later.