Sketchpad online 5.1 code#
Sketchpad online 5.1 trial#

They are elements that are not currently embedded in the page (the DOM tree), but that do exist in the JavaScript workspace.

Sketchpad online 5.1 trial#

However, when I included my trials again (each trial contains up to 10 sketchpads with images, circles and many fixdots (see example below for one) the memory increase still is dramatic quickly reaches 1GB.įab Detached elements are, in itself, normal. The upgraded version does indeed solve the memory increase during the sketchpad with text and lines. Sebastiaan thanks for the super quick action. The task then seemed to work better (students did not report crashes and the sound seemed to work fine), but the sketchpads still left detached objects and I'm unsure whether this affected the task (I ran two experiments in which I failed to obtain a fairly large effect I had obtained in 4 experiments with E-Prime with face-to-face testing or online using EPrimeGo though I can't be sure whether it reflects a problem with my programming or if memory leaks caused inaccurate response time measurements).

Sketchpad online 5.1 code#

I addressed it by replacing the sampler object with Javascript code to play the sounds (as a quick fix but I don't know if I can trust the timing accuracy of that method). In my experience, the problem has been mostly visible through sound failure and in some cases, the task crashing (I assume that sounds use up more memory). Updating to OSWeb 1.4.4.01a doesn't seem to have made a difference to the number of detached elements (so, assuming that they indicate a leak - I'm no expert -, it looks as if the problem persists). Memory use is exploding and goes up to 1GB within a minute. In the example below (I removed the task itself) I have a questionnaire with a progress bar that is updated each 250 ms. Even repeating the same sequence with sketchpads that do not contain images or sounds is increasing the consumed memory with several MB each time it is presented.

I noticed that memory leaks for images was an issue in an earlier version of OSWeb that seemed to have been addressed ( ), but it looks as if memory leaks remain present in OSWeb 1.4 (for sketchpads/feedback objects, but also for the sampler).Ī very similar case here. In the experiment I'm running now, I'm using 640 trials but I often require a lot more.

Still, the memory leaks from sketchpads/feedback objects are a concern to me as I'm worried problems will arise if I increase the number of trials. Bypassing the sampler in this way seems to work as a temporary fix (out of 40 participants, one reported a crash (but was using Safari), the other 39 reported that the sound worked throughout the experiment). For the memory leak related to the audio, I managed to eliminate it by getting rid of the sampler altogether, and using Javascript code to play sounds, after loading the sounds I need into variables (vars) from URLs point to Github resources. I've tried replacing the sketchpads with Javascript code (canvas), but the result is the same. When many trials are used, this can result in the experiment malfunctioning or crashing. However, as soon as a sequence contains more than one sketchpad, a feedback object in addition to a sketchpad, or a sampler, every execution of the sequence leaves memory leaks. With basic sequences running just a single sketchpad, there is no problem (no leak).

In that experiment (with just over 1200 trials, with 2 sketchpads, a feedback object and one sampler used in every trial), it affected about a third of the participants.

While running an experiment with OSWeb 1.4, several participants reported the task crashing or sound stimuli getting distorted or stopping playing towards the end of the experiment.