Status_Access_violation on windows

mbcerul4

Hello all,

I've uploaded by experiment to JATOS. At the moment it works fine on MozillaFirefox in Linux and Chrome in Mac, but sometimes I have problems with the experiment on Chrome in Windows. The experiment will run for a certain number of loops (around 11 loops out of 20), then an error will appear "Status_Access_Violation" and it will fail. Currently using psychopy as the backend.

Has anyone had this same problem?

I'm going to change the scratchpad elements to feedback elements to see if there is any difference, as I saw a thread saying that feedback elements don't require as much processing time or something along those lines.

mbcerul4

I noticed that when the experiment crashes, the information about what os_system and browser_version is being used is not noted. Not sure if this information is usually logged automatically at the end of the experiment, or if the experiment crashes because it's not able to identify those things in the moment the experiment is running.

sebastiaan

Hi @mbcerul4 ,

The experiment will run for a certain number of loops (around 11 loops out of 20), then an error will appear "Status_Access_Violation" and it will fail.

Do you see a more detailed error message in the developer console?

• https://osdoc.cogsci.nl/3.3/manual/osweb/osweb/#debugging

I noticed that when the experiment crashes, the information about what os_system and browser_version is being used is not noted.

That's correct. These 'context' variables are logged to the server only at the very end of the experiment.

-- Sebastiaan