Psychopy/Python - access violation reading 0x00000010












0















I use Win7, PsychoPy version 1.90.2, but the same error is also for 3.0.0b11, Standard Standalone.



When running my experiment, it crashes at certain (variable) point:



Traceback (most recent call last):
File "C:UsersMartinPsychoPyFingerTTv3FingerTTv3_lastrun.py", line 356, in <module>
win.flip()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualwindow.py", line 684, in flip
thisStim.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualtext.py", line 800, in draw
self._pygletTextObj.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletfonttext.py", line 557, in draw
self._layout.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespyglettextlayout.py", line 897, in draw
self._batch.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 560, in draw
func()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 492, in <lambda>
(lambda d, m: lambda: d.draw(m))(domain, mode))
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphicsvertexdomain.py", line 316, in draw
glDrawArrays(mode, starts[0], sizes[0])
OSError: exception: access violation reading 0x00000010


Usually 5-7 minutes after the start. I tried multiple runs, reworked whole experiment (3x), tried to isolate the issue. It crashes even when I have only the "trial-feedback" loop, so there should be the issue.



Description of the experiment
It has two routines and two loops



Routine: Trial Screen for "Trial" routine



Here, eight text items (digits) are presented, aligned horizontally at precise location. Also, there is one polygon (frame, square shape). The location of the square changes each keypress so it is under next text item (digit), sequentially from right to left and again.



The Position [x,y] of the moving frame set during every repeat from a xlsx file (column with name "Posit"), each trial, the position is updated:




$eval(Posit)




The positions in the xlsx column "Posit" look like this (normalized distances =-1,1):



Posit
(-0.42, 0.2)
(-0.3, 0.2)
(-0.18, 0.2)
(-0.06, 0.2)
(0.06, 0.2)
(0.18, 0.2)
(0.3, 0.2)
(0.42, 0.2)



The _key_press_ is just to record the pressed key and decide whether it is correct.
The last item is a picture, which is present there. Size 709x353pix and 47.7kB.



Reoutine: FB Screen for "FB" routine



The second routine is just a feedback with 0.1s duration. The picture stays the same (to avoid blinking). There is also this moving frame (which just changes color to red). And a bit of code, which is just to omit this red warning when the trial is correct. If not correct, then a variable Error increases by 1




if key_press.corr:
continueRoutine = False



else:
Error = Error+1




The _trials_Keypress_ loop makes the frame to jump to the positions from xlsx. The second lool trials is just for blocking.



Please, any idea what is wrong? I got such error also in other experiments, sometimes it was enough to rework it or rebuild it again. Thank you!!!










share|improve this question























  • Have you tried running it on other computers? Just to know if this is specific to your computer (I suspect that it is). If so, try updating your graphics drivers from the vendors website. In any case, the full set of experiment files will be helpful to debug this. It is probably better to post it on discourse.psychopy.org since this may require some back-and-forth. Delete this question or paste the Discourse link here for future interested visitors.

    – Jonas Lindeløv
    Nov 15 '18 at 13:53











  • Thank you for your suggestions. I found a post (see below), indicating that his might be due to memory leaks pertaining to textStim item. I tried to change them for a picture and the problem is gone! See more here: stackoverflow.com/questions/38101759/…

    – Makro
    Nov 16 '18 at 19:22


















0















I use Win7, PsychoPy version 1.90.2, but the same error is also for 3.0.0b11, Standard Standalone.



When running my experiment, it crashes at certain (variable) point:



Traceback (most recent call last):
File "C:UsersMartinPsychoPyFingerTTv3FingerTTv3_lastrun.py", line 356, in <module>
win.flip()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualwindow.py", line 684, in flip
thisStim.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualtext.py", line 800, in draw
self._pygletTextObj.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletfonttext.py", line 557, in draw
self._layout.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespyglettextlayout.py", line 897, in draw
self._batch.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 560, in draw
func()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 492, in <lambda>
(lambda d, m: lambda: d.draw(m))(domain, mode))
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphicsvertexdomain.py", line 316, in draw
glDrawArrays(mode, starts[0], sizes[0])
OSError: exception: access violation reading 0x00000010


Usually 5-7 minutes after the start. I tried multiple runs, reworked whole experiment (3x), tried to isolate the issue. It crashes even when I have only the "trial-feedback" loop, so there should be the issue.



Description of the experiment
It has two routines and two loops



Routine: Trial Screen for "Trial" routine



Here, eight text items (digits) are presented, aligned horizontally at precise location. Also, there is one polygon (frame, square shape). The location of the square changes each keypress so it is under next text item (digit), sequentially from right to left and again.



The Position [x,y] of the moving frame set during every repeat from a xlsx file (column with name "Posit"), each trial, the position is updated:




$eval(Posit)




The positions in the xlsx column "Posit" look like this (normalized distances =-1,1):



Posit
(-0.42, 0.2)
(-0.3, 0.2)
(-0.18, 0.2)
(-0.06, 0.2)
(0.06, 0.2)
(0.18, 0.2)
(0.3, 0.2)
(0.42, 0.2)



The _key_press_ is just to record the pressed key and decide whether it is correct.
The last item is a picture, which is present there. Size 709x353pix and 47.7kB.



Reoutine: FB Screen for "FB" routine



The second routine is just a feedback with 0.1s duration. The picture stays the same (to avoid blinking). There is also this moving frame (which just changes color to red). And a bit of code, which is just to omit this red warning when the trial is correct. If not correct, then a variable Error increases by 1




if key_press.corr:
continueRoutine = False



else:
Error = Error+1




The _trials_Keypress_ loop makes the frame to jump to the positions from xlsx. The second lool trials is just for blocking.



Please, any idea what is wrong? I got such error also in other experiments, sometimes it was enough to rework it or rebuild it again. Thank you!!!










share|improve this question























  • Have you tried running it on other computers? Just to know if this is specific to your computer (I suspect that it is). If so, try updating your graphics drivers from the vendors website. In any case, the full set of experiment files will be helpful to debug this. It is probably better to post it on discourse.psychopy.org since this may require some back-and-forth. Delete this question or paste the Discourse link here for future interested visitors.

    – Jonas Lindeløv
    Nov 15 '18 at 13:53











  • Thank you for your suggestions. I found a post (see below), indicating that his might be due to memory leaks pertaining to textStim item. I tried to change them for a picture and the problem is gone! See more here: stackoverflow.com/questions/38101759/…

    – Makro
    Nov 16 '18 at 19:22
















0












0








0








I use Win7, PsychoPy version 1.90.2, but the same error is also for 3.0.0b11, Standard Standalone.



When running my experiment, it crashes at certain (variable) point:



Traceback (most recent call last):
File "C:UsersMartinPsychoPyFingerTTv3FingerTTv3_lastrun.py", line 356, in <module>
win.flip()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualwindow.py", line 684, in flip
thisStim.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualtext.py", line 800, in draw
self._pygletTextObj.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletfonttext.py", line 557, in draw
self._layout.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespyglettextlayout.py", line 897, in draw
self._batch.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 560, in draw
func()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 492, in <lambda>
(lambda d, m: lambda: d.draw(m))(domain, mode))
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphicsvertexdomain.py", line 316, in draw
glDrawArrays(mode, starts[0], sizes[0])
OSError: exception: access violation reading 0x00000010


Usually 5-7 minutes after the start. I tried multiple runs, reworked whole experiment (3x), tried to isolate the issue. It crashes even when I have only the "trial-feedback" loop, so there should be the issue.



Description of the experiment
It has two routines and two loops



Routine: Trial Screen for "Trial" routine



Here, eight text items (digits) are presented, aligned horizontally at precise location. Also, there is one polygon (frame, square shape). The location of the square changes each keypress so it is under next text item (digit), sequentially from right to left and again.



The Position [x,y] of the moving frame set during every repeat from a xlsx file (column with name "Posit"), each trial, the position is updated:




$eval(Posit)




The positions in the xlsx column "Posit" look like this (normalized distances =-1,1):



Posit
(-0.42, 0.2)
(-0.3, 0.2)
(-0.18, 0.2)
(-0.06, 0.2)
(0.06, 0.2)
(0.18, 0.2)
(0.3, 0.2)
(0.42, 0.2)



The _key_press_ is just to record the pressed key and decide whether it is correct.
The last item is a picture, which is present there. Size 709x353pix and 47.7kB.



Reoutine: FB Screen for "FB" routine



The second routine is just a feedback with 0.1s duration. The picture stays the same (to avoid blinking). There is also this moving frame (which just changes color to red). And a bit of code, which is just to omit this red warning when the trial is correct. If not correct, then a variable Error increases by 1




if key_press.corr:
continueRoutine = False



else:
Error = Error+1




The _trials_Keypress_ loop makes the frame to jump to the positions from xlsx. The second lool trials is just for blocking.



Please, any idea what is wrong? I got such error also in other experiments, sometimes it was enough to rework it or rebuild it again. Thank you!!!










share|improve this question














I use Win7, PsychoPy version 1.90.2, but the same error is also for 3.0.0b11, Standard Standalone.



When running my experiment, it crashes at certain (variable) point:



Traceback (most recent call last):
File "C:UsersMartinPsychoPyFingerTTv3FingerTTv3_lastrun.py", line 356, in <module>
win.flip()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualwindow.py", line 684, in flip
thisStim.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespsychopyvisualtext.py", line 800, in draw
self._pygletTextObj.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletfonttext.py", line 557, in draw
self._layout.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespyglettextlayout.py", line 897, in draw
self._batch.draw()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 560, in draw
func()
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphics__init__.py", line 492, in <lambda>
(lambda d, m: lambda: d.draw(m))(domain, mode))
File "C:Program Files (x86)PsychoPy3libsite-packagespygletgraphicsvertexdomain.py", line 316, in draw
glDrawArrays(mode, starts[0], sizes[0])
OSError: exception: access violation reading 0x00000010


Usually 5-7 minutes after the start. I tried multiple runs, reworked whole experiment (3x), tried to isolate the issue. It crashes even when I have only the "trial-feedback" loop, so there should be the issue.



Description of the experiment
It has two routines and two loops



Routine: Trial Screen for "Trial" routine



Here, eight text items (digits) are presented, aligned horizontally at precise location. Also, there is one polygon (frame, square shape). The location of the square changes each keypress so it is under next text item (digit), sequentially from right to left and again.



The Position [x,y] of the moving frame set during every repeat from a xlsx file (column with name "Posit"), each trial, the position is updated:




$eval(Posit)




The positions in the xlsx column "Posit" look like this (normalized distances =-1,1):



Posit
(-0.42, 0.2)
(-0.3, 0.2)
(-0.18, 0.2)
(-0.06, 0.2)
(0.06, 0.2)
(0.18, 0.2)
(0.3, 0.2)
(0.42, 0.2)



The _key_press_ is just to record the pressed key and decide whether it is correct.
The last item is a picture, which is present there. Size 709x353pix and 47.7kB.



Reoutine: FB Screen for "FB" routine



The second routine is just a feedback with 0.1s duration. The picture stays the same (to avoid blinking). There is also this moving frame (which just changes color to red). And a bit of code, which is just to omit this red warning when the trial is correct. If not correct, then a variable Error increases by 1




if key_press.corr:
continueRoutine = False



else:
Error = Error+1




The _trials_Keypress_ loop makes the frame to jump to the positions from xlsx. The second lool trials is just for blocking.



Please, any idea what is wrong? I got such error also in other experiments, sometimes it was enough to rework it or rebuild it again. Thank you!!!







python psychopy






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 10:17









MakroMakro

11




11













  • Have you tried running it on other computers? Just to know if this is specific to your computer (I suspect that it is). If so, try updating your graphics drivers from the vendors website. In any case, the full set of experiment files will be helpful to debug this. It is probably better to post it on discourse.psychopy.org since this may require some back-and-forth. Delete this question or paste the Discourse link here for future interested visitors.

    – Jonas Lindeløv
    Nov 15 '18 at 13:53











  • Thank you for your suggestions. I found a post (see below), indicating that his might be due to memory leaks pertaining to textStim item. I tried to change them for a picture and the problem is gone! See more here: stackoverflow.com/questions/38101759/…

    – Makro
    Nov 16 '18 at 19:22





















  • Have you tried running it on other computers? Just to know if this is specific to your computer (I suspect that it is). If so, try updating your graphics drivers from the vendors website. In any case, the full set of experiment files will be helpful to debug this. It is probably better to post it on discourse.psychopy.org since this may require some back-and-forth. Delete this question or paste the Discourse link here for future interested visitors.

    – Jonas Lindeløv
    Nov 15 '18 at 13:53











  • Thank you for your suggestions. I found a post (see below), indicating that his might be due to memory leaks pertaining to textStim item. I tried to change them for a picture and the problem is gone! See more here: stackoverflow.com/questions/38101759/…

    – Makro
    Nov 16 '18 at 19:22



















Have you tried running it on other computers? Just to know if this is specific to your computer (I suspect that it is). If so, try updating your graphics drivers from the vendors website. In any case, the full set of experiment files will be helpful to debug this. It is probably better to post it on discourse.psychopy.org since this may require some back-and-forth. Delete this question or paste the Discourse link here for future interested visitors.

– Jonas Lindeløv
Nov 15 '18 at 13:53





Have you tried running it on other computers? Just to know if this is specific to your computer (I suspect that it is). If so, try updating your graphics drivers from the vendors website. In any case, the full set of experiment files will be helpful to debug this. It is probably better to post it on discourse.psychopy.org since this may require some back-and-forth. Delete this question or paste the Discourse link here for future interested visitors.

– Jonas Lindeløv
Nov 15 '18 at 13:53













Thank you for your suggestions. I found a post (see below), indicating that his might be due to memory leaks pertaining to textStim item. I tried to change them for a picture and the problem is gone! See more here: stackoverflow.com/questions/38101759/…

– Makro
Nov 16 '18 at 19:22







Thank you for your suggestions. I found a post (see below), indicating that his might be due to memory leaks pertaining to textStim item. I tried to change them for a picture and the problem is gone! See more here: stackoverflow.com/questions/38101759/…

– Makro
Nov 16 '18 at 19:22














0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317140%2fpsychopy-python-access-violation-reading-0x00000010%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317140%2fpsychopy-python-access-violation-reading-0x00000010%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Xamarin.iOS Cant Deploy on Iphone

Glorious Revolution

Dulmage-Mendelsohn matrix decomposition in Python