URL of experiment: https://gitlab.pavlovia.org/eeshanhasan/a-test-project
Description of the problem: I wanted to have a drag and drop component in an experiment. This involves me setting the position of the text equal to that of the mouse pointer. I realised that this was creating a memory leak. This is the smallest example that has the error. Am I doing something wrong?
Your repository isn’t public, so we can’t see it. It might be something you’re doing, but it looks like there are a few people having problems with code that updates every frame.
@jon is this a similar root issue to Pavlovia: black screen and unable to continue (RAM issues)?
I have made it public. Forgot to press ‘save changes’ last time.
It seems to be heaping and creating more nodes for some reason. This memory leak goes pretty quickly.
OK. @jon @apitiot this one is a real issue.
I took your code and modified it further. If you update a property of the textstim object, even with something as simple as textstim.pos = textstim.pos, you get this behavior. The good news is that it’s not the mouse doing it, you can have it call mouse.getPos() and you don’t get this as long as you then don’t try to use that information to set the position of the text stimulus.
So it’s updating the text stimulus on every frame that’s behind this memory leak. Why I’m not sure, but that’s where we’re at.
Thank you. This might be a problem with any of the set functions.
Thanks for the info on that guys. What browser/OS was this on?
Looks like Chrome for both of us based on the debugger, for OS I’m on MacOS High Sierra.
I checked and this problem happens with Firefox as well.
I am on Mojave 10.14.6.
Chrome Version Version 80.0.3987.149 (Official Build) (64-bit)
Firefox 74.0 (64-bit)
