Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

OpenSesame crashes when emptying unused item bin

edited March 2016 in OpenSesame

Hello everyone,

After copying an experiment to a new default template we ended up with a full bin of unused items (54 items). For the sake of orderliness we want to permanently delete them. But when deleting the items the program stops responding after a few moments, and the only way out is force quitting the program. Deleting a single item from the bin starts with the same procedure but after almost 10 minutes OpenSesame resumes activity and the item is permanently deleted.

OpenSesame is updated to the latest version and running on Windows.

Any idea what is going on here? Is it dependent on the content of the unused bin? The experiment is rather large due to a large file pool (about 18MB) but otherwise works perfectly.

Thanks in advance,

Laurent

Comments

  • edited 6:03AM

    Hi Laurent,

    This sounds like some kind of recursion check run amok, that is, checking which item uses which item, which uses which item, etc. This has a tendency to become exponentially slow. However, I cannot reproduce it myself. Could you upload the script so that I can see exactly what's going on?

    Cheers,
    Sebastiaan

    PS. I noticed that you've been helping out some people on here the forum. Thanks--it's much appreciated!

  • edited 6:03AM

    Hi Sebastiaan,

    There are indeed a lot of unnecessary loops and sequences in the unused item bin. The experiment script can be found here.I don't have permission to upload the filepool along with it unfortunately.

    My best guess is that by merging two experiment, two main experiment loops (including all items) ended up in the unused bin but they should have been overwritten and permanently deleted instead.

    Anyway, thanks for checking the script!

    I'm happy helping around btw, it's a nice way to learn some OS/Python myself :)

    Cheers,
    Laurent

  • edited April 2016

    Hi,

    I can confirm that bug when the tash bin (unused items) gets to large. last time we fixed this by deleting the items singularly. this time this seems to crash as well.

    Is there a way to access the trash bin from windows?

    Best,
    Daniel

    -- EDIT --

    you can delete unused items by deleting their definitions via experiment -> general properties -> script editor.

    there check for your items by searching their definition and delete.

  • Hey Sebastiaan,
    many thanks for this powerful and easy doing software! It is great!
    At the moment i am still marvelling about the unused item bin.
    First of all: The unused items bin is great to use :)
    I can put some items down, and run the experiment "without" these items. Later i just pick them again.

    However i found things you 'd might be interested in:
    1. There are variables defined in items in the unused items bin. All of them appear in the logfile. That should not be the case, i think.
    2. When i import something in the unused items, i get an error message, when i try to run the experiment.
    Because it does not import (it is in the bin), the not imported command is unknown.
    3. I concluded that the unused items bin is read, when running the experiment. But this is not necesary. And sometimes leads to problems (e.g. if the script in the bin is incomplete).

    Info: I am using many inline_scripts ;)
    Cheers
    Stephan

Sign In or Register to comment.