Possible movie3.py-related crashes

OS: Windows 10

PsychoPy version: 2020.2.4

Standard Standalone? yes

What are you trying to achieve?: Play combination of .wav and .mpeg files to create blocks of audio-only, visual-only, and audiovisual stimuli

What did you try to make it work?:
Hello!
I have a very simple flow set up in builder right now which just consists of alternating routines to present instructions for each block then loop though a list of stimuli and collect keyboard responses for each trial (eventually I’ll add an outer loop to randomize the order the conditions are presented in across participants). As I was building the task, I initially constructed each condition type in separate files for easier testing and they all worked fine. I then rebuilt each of those components into a new file with the combined flow seen here and loaded in shortened conditions files (5 trials each) to test the full run (without subjecting myself to hundreds of McGurk videos!).


What specifically went wrong when you tried that?:

Now, when I try to run the full version, it runs through the first two conditions (audio-only and visual-only) but crashes before moving into the audiovisual block’s instructions. Given the timing of the crash and the error message I receive (below) I am wondering if it may be something to do with the video files depleting memory space as discussed in this thread - Error with demo code moviestim2 on psychopy 1.90.3 (on windows OS) - #3 by zoubochao? However, I am able to run the full set of video stimuli (many more than 5 trials) in the file I built to test this condition alone so I’m not sure if that’s it.

Any insight on what this issue might be or how to address it within the builder would be very much appreciated!

Error Message
Welcome to PsychoPy3!
v2020.2.4
143.1973 INFO Loaded monitor calibration from [‘2020_01_28 14:18’]
483.0498 EXP Imported C:\Users\csala\OneDrive\Desktop\Online_McGurkandSentences_Expt\McGurk\OLAVS_stim_AOCond_ShortTest.csv as conditions, 5 conditions, 16 params
Generating PsychoPy script…

Running: C:\Users\csala\OneDrive\Desktop\Online_McGurkandSentences_Expt\McGurk\OnlineMGTaskShortTEST2_lastrun.py ##
574.1051 INFO Loaded monitor calibration from [‘2020_01_28 14:18’]
pygame 1.9.6
Hello from the pygame community. Contribute - pygame wiki
16.8072 WARNING User requested fullscreen with size [1504 1003], but screen is actually [2256, 1504]. Using actual size
Traceback (most recent call last):
File “C:\Users\csala\OneDrive\Desktop\Online_McGurkandSentences_Expt\McGurk\OnlineMGTaskShortTEST2_lastrun.py”, line 705, in
depth=0.0,
File “C:\Program Files\PsychoPy3\lib\site-packages\psychopy\visual\movie3.py”, line 140, in init
self.loadMovie(self.filename)
File “C:\Program Files\PsychoPy3\lib\site-packages\psychopy\visual\movie3.py”, line 182, in loadMovie
if os.path.isfile(filename):
File “C:\Program Files\PsychoPy3\lib\genericpath.py”, line 30, in isfile
st = os.stat(path)
TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType
Exception ignored in: <bound method MovieStim3.del of <psychopy.visual.movie3.MovieStim3 object at 0x000001E21F230EF0>>
Traceback (most recent call last):
File “C:\Program Files\PsychoPy3\lib\site-packages\psychopy\visual\movie3.py”, line 498, in del
self._unload()
File “C:\Program Files\PsychoPy3\lib\site-packages\psychopy\visual\movie3.py”, line 476, in _unload
self.clearTextures()
File “C:\Program Files\PsychoPy3\lib\site-packages\psychopy\visual\basevisual.py”, line 1016, in clearTextures
GL.glDeleteTextures(1, self._texID)
OSError: exception: access violation reading 0x0000000000000000

Experiment ended.

It looks like the movie is being initialised with the file set to “None”, if you look at the experiment code are there any calls to psychopy.MovieStim where the movie file is None? Please feel free to send over the .py or .psyexp file and I can have a closer look myself

Hello, I’m sorry for my slow reply. I actually found that something had been corrupted in one of the conditions files and I was able to get in running again.

Thank you for offering to help anyway, I’m sure I’ll be back on the discourse with new problems in the future!