Howdy, Stranger!

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

Supported by

OpenSesame 2.9.6 app available for OSX

edited February 2016 in OpenSesame

The OSX app of OpenSesame 2.9.6. has been released! It was a bumpy road to get there, and the result still isn't perfect, but getting very close.

The latest version of the OpenSesame app has been composed on OS X Yosemite (10.10). Initial tests have shown that the app also appears to run well on Mavericks (10.9). If you experience problems starting or using the app when you have an OS X version older than Mavericks, we recommend you to upgrade to a newer version of OS X (after all, Mavericks and Yosemite are both free) or use one of the older releases of OpenSesame for Mac.

A caveat of this version of the OpenSesame app is that the multiprocess implementation is not yet working (this does work well if you run OpenSesame from source). We hope to have this fixed in one of the next releases, but for now you will have to stick to the inprocess runner.

Please test this app and provide your feedback here!

Updated by @sebastiaan for 2.9.6


  • edited 1:25AM

    Thanks for your great work on this, Daniel! :)>-

  • edited 1:25AM

    Everything started fine. I was learning how to use OpenSesame. But, then, it started to crash on every use. Now, I can't do anything. Anytime I try to interact with an item, OpenSesame crashes. I am using Mac OS 10.10 Yosemite.

    Here's part of the error box.

    Process: OpenSesame [632]
    Path: /Volumes/VOLUME/
    Identifier: nl.cogsci.osdoc
    Version: 2.9.6 (2.9.6)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: OpenSesame [632]
    User ID: 501

    Date/Time: 2015-06-03 15:28:07.886 +0200
    OS Version: Mac OS X 10.10.3 (14D136)
    Report Version: 11
    Anonymous UUID: 516182FE-FDB8-422F-8BA4-4232689BFEE2

    Time Awake Since Boot: 1700 seconds

    Crashed Thread: 0 Dispatch queue:

    Exception Type: EXC_BAD_ACCESS (SIGABRT)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

    VM Regions Near 0x18:
    __TEXT 0000000100000000-000000010000a000 [ 40K] r-x/rwx SM=COW /Volumes/VOLUME/

    Application Specific Information:
    abort() called

    Thread 0 Crashed:: Dispatch queue:
    0 libsystem_kernel.dylib 0x00007fff90884286 pthread_kill + 10
    1 libsystem_c.dylib 0x00007fff8de3ab53 abort + 129
    2 org.python.python 0x00000001047f1a9a Py_FatalError + 49
    3 libsystem_platform.dylib 0x00007fff90d61f1a _sigtramp + 26
    4 ??? 0x00007fff3f800000 0 + 140734258741248
    5 0x00007fff8a7bee59 -[NSWindow(NSDrag) dragImage:at:offset:event:pasteboard:source:slideBack:] + 135
    6 QtGui 0x0000000105b97963 0x105b6c000 + 178531
    7 QtGui 0x0000000105bf2d7b QDrag::start(QFlags) + 73
    8 0x00000001054e63c6 0x105450000 + 615366
    9 org.python.python 0x00000001047d6979 PyEval_EvalFrameEx + 14227
    10 org.python.python 0x00000001047d96d1 0x10474f000 + 566993
    11 org.python.python 0x00000001047d6553 PyEval_EvalFrameEx + 13165
    12 org.python.python 0x00000001047d2fb4 PyEval_EvalCodeEx + 1387
    13 org.python.python 0x0000000104777bf5 0x10474f000 + 166901
    14 org.python.python 0x0000000104759ad7 PyObject_Call + 99
    15 org.python.python 0x0000000104764962 0x10474f000 + 88418
    16 org.python.python 0x0000000104759ad7 PyObject_Call + 99
    17 org.python.python 0x00000001047d8e2e PyEval_CallObjectWithKeywords + 93
    18 0x00000001053846cd sip_api_invoke_slot_ex + 439
    19 0x0000000104f79966 PyQtProxy::invokeSlot(qpycore_slot const&, void**, int) + 162
    20 0x0000000104f79832 PyQtProxy::unislot(void) + 184
    21 0x0000000104f79769 PyQtProxy::qt_metacall(QMetaObject::Call, int, void
    ) + 111
    22 QtCore 0x00000001051b6c8d QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1809
    23 0x0000000104f4c680 sipQTimer::timerEvent(QTimerEvent*) + 98
    24 QtCore 0x00000001051b2fe3 QObject::event(QEvent*) + 51
    25 0x0000000104f4c614 sipQTimer::event(QEvent*) + 98
    26 QtGui 0x0000000105be6ed5 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 195
    27 QtGui 0x0000000105be8419 QApplication::notify(QObject*, QEvent*) + 889
    28 0x0000000105494a24 sipQApplication::notify(QObject*, QEvent*) + 122
    29 QtCore 0x00000001051a2bb8 QCoreApplication::notifyInternal(QObject*, QEvent*) + 118
    30 QtGui 0x0000000105bea1ba 0x105b6c000 + 516538
    31 QtGui 0x0000000105ba3f01 0x105b6c000 + 229121
    + 20
    33 0x00007fff904edf73 __CFRunLoopDoTimer + 1059
    34 0x00007fff9056153d __CFRunLoopDoTimers + 301
    35 0x00007fff904a9608 __CFRunLoopRun + 2024
    36 0x00007fff904a8bd8 CFRunLoopRunSpecific + 296
    37 0x00007fff8969756f RunCurrentEventLoopInMode + 235
    38 0x00007fff896972ea ReceiveNextEventCommon + 431
    39 0x00007fff8969712b _BlockUntilNextEventMatchingListInModeWithFilter + 71
    40 0x00007fff8a59a9bb _DPSNextEvent + 978
    41 0x00007fff8a599f68 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
    42 0x00007fff8a58fbf3 -[NSApplication run] + 594
    43 QtGui 0x0000000105ba4936 0x105b6c000 + 231734
    44 QtCore 0x00000001051a0215 QEventLoop::processEvents(QFlags) + 77
    45 QtCore 0x00000001051a0386 QEventLoop::exec(QFlags) + 356
    46 QtCore 0x00000001051a3009 QCoreApplication::exec() + 199
    47 0x0000000105495be2 0x105450000 + 285666
    48 org.python.python 0x00000001047d6979 PyEval_EvalFrameEx + 14227
    49 org.python.python 0x00000001047d2fb4 PyEval_EvalCodeEx + 1387
    50 org.python.python 0x00000001047d6ff9 PyEval_EvalFrameEx + 15891
    51 org.python.python 0x00000001047d2fb4 PyEval_EvalCodeEx + 1387
    52 org.python.python 0x00000001047d9640 0x10474f000 + 566848
    53 org.python.python 0x00000001047d6553 PyEval_EvalFrameEx + 13165
    54 org.python.python 0x00000001047d2fb4 PyEval_EvalCodeEx + 1387
    55 org.python.python 0x00000001047d2a43 PyEval_EvalCode + 54
    56 org.python.python 0x00000001047f2816 0x10474f000 + 669718
    57 org.python.python 0x00000001047f28b9 PyRun_FileExFlags + 133
    58 org.python.python 0x00000001047f23f9 PyRun_SimpleFileExFlags + 711
    59 nl.cogsci.osdoc 0x000000010000275b py2app_main + 2683
    60 nl.cogsci.osdoc 0x000000010000117a main + 650
    61 nl.cogsci.osdoc 0x0000000100000be4 start + 52

  • edited 1:25AM

    It seems to be working fine on my machine. I'm wondering though, why the Pygaze plug-ins aren't installed. I'm having some trouble with getting the pygaze stuff to work in a Mac environment. I was hoping this might be a solution. Has anyone figured this out?


  • edited 1:25AM

    @DaniCook strange. This should not happen! If it worked before but not now, then I have a hunch that it might be that your hard disk is getting a bit full and OpenSesame does not have enough space to extract its experiments into a temp folder it requires... Can you check that first?

    @MichealP Good idea. Next releases I'll include the pygaze plugin. You can for now easily install plugins on OS X by creating a .opensesame/plugins folder in your home dir (don't forget the period in front of opensesame: it is a hidden folder) and then extract the pygaze plugin folders in there!

  • edited 1:25AM

    opensesamerun seems to be missing from the current OS X package. I discovered this when trying to run a script via the external option preference. This took some work because the OSError was hard to get a traceback on (well, the standard functions kept giving me an empty traceback).

    I finally tracked down the generator of the OSErrorto the call to subprocess.Popen(). At first I thought it might be stdout that was missing, but I reduced the call down to p = subprocess.Popen(self.cmd) and still had the same problem. Looking through the app contents, I couldn't find opensesamerun.

    Two possible fixes: warn on selecting external runner (as is currently done for multiprocess) or include opensesamerun in the package.

    Otherwise, everything seems to be working great in initial testing on OS X 10.10 Yosemite!

  • edited 1:25AM

    You are right about opensesamerun; it is one of the negative consequences in the way apps are created on OSX: parts of the program 'inside' the app package are difficult to access or run. I could try to package opensesamerun separately (as a standalone app) in the future, but I doubt that it can be easily started from within the main OpenSesame app (as command line arguments, such as the filename of the experiment that needs to be run, cannot be easily passed to an app as far as I know). Anyway, we'll still have to come up with a permanent solution to get OpensesameRun to work again, but for the moment there isn't any.

  • edited 1:25AM

    The download link appears to be down at the moment.

  • edited 1:25AM

    I can download the installer from the link. Are you sure it wasn't something temporary with your browser, or such?


  • edited 1:25AM

    I've now found it on several computers, including for the base URL, although they were all from within my university system so maybe there's some weird firewall nonsense happening. However I checked and got, "It's not just you! looks down from here."

  • edited 1:25AM

    @drsaunders You're right, the download link was broken ( is down) and then fixed in the 2.9 docs, but I hadn't merged this into the 3.0 docs. It should be fixed now.

  • edited 1:25AM

    Ah okay. But why can I then access ems? Is it because I'm in the VU network?

  • edited 1:25AM

    Ah okay. But why can I then access ems? Is it because I'm in the VU network?

    Yes, I suppose so then.

  • edited 1:25AM

    Because of some internal changes to the VU network (mainly firewall stuff), the address at which the mac version of OpenSesame was served is no longer accessible. We are working on a different solution, or rather a different location to host the OSX version of OpenSesame on, which can be reached from everywhere but it is not available yet. Once it is we will put a notification on the forum and place a correct link to it on the main website again.

This discussion has been closed.