spyder: Spyder crashes at startup in new conda environment python 3.4 on Windows 8.1 x64
(1). The bug
I create a new environment with conda create --name testspyder python=3.4 spyder
then I activate testspyder. When I don’t specify spyder version, 2.3.8 is installed (spyder=2.3.8=py34_0).
When I try to start spyder in this environment, it crashes at startup, showing a Windows popup saying python.exe has stopped working. There is no console output with --show-console.
When I try to debug it with Microsoft Visual Studio 2015 (suggested to me by the debug button in the Windows popup), the following message appears:
Unhandled exception at 0x0000000063B347AF (QtGui4.dll) in python.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
According to this message the problem seems to be related to Qt.
The same problem occurs with spyder 2.3.7 (spyder=2.3.7=py34_3):
conda create --name testspyder python=3.4 spyder=2.3.7
(2). Package version comparison My spyder 2.3.7 is running OK in my “stable” environment. This stable environment is created with installing the anaconda meta package. From continuum.io:
The anaconda metapackage is designed for people who want to keep a stable set of packages, which have been tested together.
I decided to make 2 packages versions comparison:
- between my stable environment and
conda create --name testspyder python=3.4 spyder(2.3.8) - between my stable environment and
conda create --name testspyder python=3.4 spyder=2.3.7
I only listed the packages common to the 2 compared environments AND with different versions.
- anaconda stable vs
conda create --name testspyder python=3.4 spyder
name: stable name: testspyder (2.3.8)
dependencies: dependencies:
- libtiff=4.0.6=vc10_0 - libtiff=4.0.6=vc10_1
- msvc_runtime=1.0.0=vc10_0 - msvc_runtime=1.0.1=vc10_0
- path.py=8.1.2=py34_0 - path.py=8.1.2=py34_1
- psutil=3.2.2=py34_0 - psutil=3.3.0=py34_0
- pyqt=4.11.4=py34_2 - pyqt=4.11.4=py34_4
- python=3.4.3=3 - python=3.4.3=5
- pytz=2015.6=py34_0 - pytz=2015.7=py34_0
- qt=4.8.7=vc10_4 - qt=4.8.7=vc10_5
- qtconsole=4.1.0=py34_0 - qtconsole=4.1.1=py34_0
- setuptools=18.4=py34_0 - setuptools=18.5=py34_0
- sip=4.16.9=py34_1 - sip=4.16.9=py34_2
- spyder=2.3.7=py34_3 - spyder=2.3.8=py34_0
- anaconda stable vs
conda create --name testspyder python=3.4 spyder=2.3.7
name: stable name: testspyder (2.3.7)
dependencies: dependencies:
- libtiff=4.0.6=vc10_0 - libtiff=4.0.6=vc10_1
- msvc_runtime=1.0.0=vc10_0 - msvc_runtime=1.0.1=vc10_0
- path.py=8.1.2=py34_0 - path.py=8.1.2=py34_1
- psutil=3.2.2=py34_0 - psutil=3.3.0=py34_0
- pyqt=4.11.4=py34_2 - pyqt=4.11.4=py34_4
- python=3.4.3=3 - python=3.4.3=5
- pytz=2015.6=py34_0 - pytz=2015.7=py34_0
- qt=4.8.7=vc10_4 - qt=4.8.7=vc10_5
- qtconsole=4.1.0=py34_0 - qtconsole=4.1.1=py34_0
- setuptools=18.4=py34_0 - setuptools=18.5=py34_0
- sip=4.16.9=py34_1 - sip=4.16.9=py34_2
I hope this helps. If this is not a spyder bug, then I hope this will help to identify the Qt / PyQt / ? bug. This issue seems to be differs from https://github.com/spyder-ide/spyder/issues/2834 since PyQwt is not installed in any of the 3 environments I present.
About this issue
- Original URL
- State: closed
- Created 11 years ago
- Comments: 16 (5 by maintainers)
I was having a similar problem. Using the above information, I ran
conda remove qt --name py34andconda install qt=4.8.7=vc10_4to fix the issue.I am running Windows 7 with Anaconda where the root is python 3.5 and the installed environment is python 3.4. Spyder ran fine on the root and
spyder environment python.exe has stopped workingappeared when attempting to run Spyder for the environment.