Multiple crash (Windows 10)

Th.Hinault · October 2016

Hi everyone,
I contact you because I can't lauch OpenSesame on my windows 10 laptop anymore.
When I click on the icon I can see that something is loading but the program never starts.
If I look at the task manager I can see the "opensesame" and "pythonw" processes for a few seconds before they disappear.
Everything worked fine the last time I checked (one week ago).
Do you know what can cause these crashes ? Could it be a windows update ? What can I do ?

Thanks,

Thomas

sebastiaan · October 2016

Hi Thomas,

As a first step, you can start OpenSesame via the command prompt. Presumably, OpenSesame will still crash, but then at least you can see the error message. Under Windows 7 (and presumably 10 as well), you can start the command prompt by running cmd.exe. Then, you first go to where OpenSesame is installed, like so (if you've installed to the default location):

cd "\Program Files (x86)\OpenSesame"

And then you run OpenSesame as follows (i.e. as though it is Python script--which it is):

python Scripts\opensesame-script.py

What happens if you do that?

Cheers!
Sebastiaan

Th.Hinault · October 2016

Hi Sebastiaan,
I tried what you asked.
On the cmd I got "WARNING:root:Message signing is disabled. This is insecure and not recommanded!"
I also got a windows message "Python.exe ceased functionning".
So it appear that the problem comes from Python and not OpenSesame. Should I try to reinstall it ?

Thanks (et bon voyage ! I hope that you appreciated your time at Marseille !)
Thomas

sebastiaan · October 2016

Hi Thomas,

This:

WARNING:root:Message signing is disabled. This is insecure and not recommanded!

Is normal. I'm not sure where it comes from actually, I suspect from the OSF extension.

In any case, this:

Python.exe ceased functionning

Is clearly the problem, because it means that Python itself has crashed; that is, not a bug in one of the Python scripts, but in the Python interpreter itself. You can try re-installing, but I doubt it will make any difference. Another option is to try the Python 3-based version.

et bon voyage ! I hope that you appreciated your time at Marseille !

Sure did! And I hope that you enjoy your time in Montreal!

Cheers!
Sebastiaan

Th.Hinault · October 2016

Yes Montreal is great !
I installed OpenSesame for Python 3.5 (and I installed the latest version of Python).
Now Open Sesame lanche a black command window but nothing happens...

sebastiaan · October 2016

Now Open Sesame lanche a black command window but nothing happens...

Ok that's probably the same issue then. The Python 3 package (for now) always opens a command window as a result of how it's packaged. Do you see any output in the command window?

What happens if you start python.exe directly? Do you even get a working Python prompt?

(and I installed the latest version of Python)

Just to avoid confusion: OpenSesame comes with its own Python environment (a miniconda environment to be exact). So you don't need to install Python yourself; not that doing so interferes with OpenSesame, but it's just not necessary.

Th.Hinault · October 2016

Ok so I removed Python.
If I start python.exe directly I got a working Python prompt. However, nothing happens when I try to start pythonw.

sebastiaan · October 2016

I installed OpenSesame for Python 3.5 (and I installed the latest version of Python). Now Open Sesame lanche a black command window but nothing happens...

Yesterday, right after the release of 3.1.3, I uploaded a Python 3 package that didn't work. This was opensesame_3.1.3-py3.5-win64-1.zip, that is, ending in 1. Is that the one you tried? If so, please download the updated package opensesame_3.1.3-py3.5-win64-2.zip, that is, ending in 2. (The last number indicates the package version. For example, if, as happened yesterday, someone makes a mistake in the packaging process, the same version of software is packaged again, and only the package version is updated.)

Other than that, could you give some more details on your system? What version of Windows are you using exactly? I've heard reports of OpenSesame not starting on Windows 10 before, so any information would be helpful.

Th.Hinault · October 2016

I'm on Windows 10, version 1607 (OS version 14393.321).
I uninstalled my previous version of Open Office to install the package 2. It's working !
My problem now is that I can't start my experiments, I get the following error :

Failed to parse experiment for the following reason:

Unexpected error
Details

time: Sat Oct 22 08:51:14 2016
exception type: ValueError
exception message: stat: path too long for Windows
item-stack: ``
Traceback (also in debug window)

File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libqtopensesame\runners\base_runner.py", line 221, in init_experiment
logfile=logfile)
File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\experiment.py", line 139, in init
string = self.open(string)
File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\experiment.py", line 627, in open
if not os.path.exists(src):
File "C:\Program Files (x86)\OpenSesame\lib\genericpath.py", line 19, in exists
os.stat(path)
ValueError: stat: path too long for Windows

I tried to indicate "python.exe" from the open office folder in the path (environment variables) but this is not working ...

sebastiaan · October 2016

Hi Thomas,

I've heard about this error before. It seems to be specific to Windows 10, or at least I cannot reproduce it. If you open this file:

C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\experiment.py"

In a text editor, and change this part (on line 627):

        if not os.path.exists(src):
            debug.msg(u'opening from unicode string')
            self.experiment_path = None
            return safe_decode(src, errors=u'replace')

To this:

        try:
            if not os.path.exists(src):
                raise ValueError('Path doesn\'t exist)')
        except (ValueError, osexception): 
            debug.msg(u'opening from unicode string')
            self.experiment_path = None
            return safe_decode(src, errors=u'replace')

Does that solve the issue?

Cheers,
Sebastiaan

Th.Hinault · October 2016

No, when I change this the program does not start anymore.

Howdy, Stranger!

Categories

Multiple crash (Windows 10)

Comments

Howdy, Stranger!

Quick Links

Categories

Multiple crash (Windows 10)

Comments