Howdy, Stranger!

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

Supported by

[open] 2.9.x running very slow.

edited January 2015 in OpenSesame

Hi all. I'm trying to edit an old program made with (I think) 2.8.3, and when I open it with a newer version, everything runs very slow with lots of (Not Responding) errors. It crashes often and can take up to several minutes to complete a single operation.

I'd be fine with just reinstalling 2.8.3, but the edits I'm making would be much easier with the ctrl+shift copy function that allows you to copy an item under a new name. I can't seem to get that to work in the old version.

I can upload the program if you wish, but it's quite messy right now since it was in the middle of edits that required a bunch of duplication and then trimming of the duplicated items.

Thanks for any help, and I'll keep working on it with the old version for now.

Edit2: I think I should also note that we've tried this across several computers, including one with a Haswell i5 and 8GB RAM.

Comments

  • edited 8:26PM

    So, I found a way around this and just created new items where necessary and appended the appropriate child objects to them. So I don't have a problem personally, but maybe someone else has an issue with old programs not running properly on the new version.

  • edited 8:26PM

    Hi,

    There have been reports before of very poor performance with large experiments. Performance becomes so poor that it's a problem even on a very fast computer. Am I correct in assuming that you have lots of items in your experiment?

    When you say 'crash', does it really crash, or does it just never complete an operation? If it crashes, what happens exactly? And what kind of operations trigger the problem? This information will help to narrow the issue down, which has been filed here [#305].

    Cheers,
    Sebastiaan

  • edited 8:26PM

    Yes, it's a very big experiment with lots of items (most of them duplicates or repeats of a single item, but it is very large).

    When I said crash, I mean that Windows views it as "not responding" and it creates the spinning death cursor. Pretty much any operation could trigger this, opening the program would even take several minutes. Most of the time it went into "not responding", it was when I was duplicating an item or opening an item. Hope that helps!

  • edited 8:26PM

    I found and fixed at least one bottleneck in terms of performance. Would you mind checking if your experience is better with the latest 2.9.3 prerelease?

Sign In or Register to comment.