0.99.1 crashes python on Windows XP [SEC=UNCLASSIFIED]

Hi Listers,

I recently installed matplotlib 0.99.1 hoping to use mplot3d. However, when doing 'from mpl_toolkits.mplot3d import Axes3D' python itself crashes. Reinstalling matplotlib 0.98.5 gets everything working fine, without mplot3d, of course.

I am running Windows XP, python 2.5.2 and numpy 1.2.1. From the installation instructions I think I have all the prerequisites.

Has anyone seen behaviour like this?

Ross Wilson

Hi Everyone,

Hi Listers,

I recently installed matplotlib 0.99.1 hoping to use mplot3d. However, when doing 'from mpl_toolkits.mplot3d import Axes3D' python itself crashes. Reinstalling matplotlib 0.98.5 gets everything working fine, without mplot3d, of course.

I am running Windows XP, python 2.5.2 and numpy 1.2.1. From the installation instructions I think I have all the prerequisites.

Has anyone seen behaviour like this?
   

It looks like I run into a similar issue on a client machine.

He is on Windows XP SP 2 Suisse edition and he gets "Unhandled Exception" error which does not show any traceback.

My application is py2exe'd, so I did another build using 0.98.5 (both with numpy 1.3, Python 2.5.4 and wxPython 2.8.10) but now at least we get a traceback:

Traceback (most recent call last):
   File "appwine.pyo", line 939, in OnToolbarChart
   File "zipextimporter.pyo", line 82, in load_module
   File "frameplotmpl.pyo", line 24, in<module>
ImportError: cannot import name FigureCanvasWxAgg

The relevant section of frameplotmpl.py is:
from numpy import arange, sin, pi
import matplotlib as mpl
# following is already done on stats page
##mpl.use('WXAgg')
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx
from matplotlib.dates import YearLocator, MonthLocator, DateFormatter
from matplotlib.ticker import FormatStrFormatter
from matplotlib.font_manager import FontProperties

What is really strange I can run the same .exe on my XP test machine which is running XP SP2 English without any problems.

I know there is not much to go by here, but would very much appreciate if anyone has some hints/tips on what I should look at (note that the client is non technical and I have no access to his machine).

Werner

···

On 08/10/2009 06:54, Ross.Wilson@...2808... wrote:

The user has an AMD CPU, could this be related to the numpy issue with AMD machines?

Werner

···

On 18/02/2010 15:12, Werner F. Bruhin wrote:

Hi Everyone,

On 08/10/2009 06:54, Ross.Wilson@...2808... wrote:
   

Hi Listers,

I recently installed matplotlib 0.99.1 hoping to use mplot3d. However, when doing 'from mpl_toolkits.mplot3d import Axes3D' python itself crashes. Reinstalling matplotlib 0.98.5 gets everything working fine, without mplot3d, of course.

I am running Windows XP, python 2.5.2 and numpy 1.2.1. From the installation instructions I think I have all the prerequisites.

Has anyone seen behaviour like this?

It looks like I run into a similar issue on a client machine.

He is on Windows XP SP 2 Suisse edition and he gets "Unhandled
Exception" error which does not show any traceback.

My application is py2exe'd, so I did another build using 0.98.5 (both
with numpy 1.3, Python 2.5.4 and wxPython 2.8.10) but now at least we
get a traceback:

Traceback (most recent call last):
    File "appwine.pyo", line 939, in OnToolbarChart
    File "zipextimporter.pyo", line 82, in load_module
    File "frameplotmpl.pyo", line 24, in<module>
ImportError: cannot import name FigureCanvasWxAgg

The relevant section of frameplotmpl.py is:
from numpy import arange, sin, pi
import matplotlib as mpl
# following is already done on stats page
##mpl.use('WXAgg')
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx
from matplotlib.dates import YearLocator, MonthLocator, DateFormatter
from matplotlib.ticker import FormatStrFormatter
from matplotlib.font_manager import FontProperties

What is really strange I can run the same .exe on my XP test machine which is running XP SP2 English without any problems.

I know there is not much to go by here, but would very much appreciate if anyone has some hints/tips on what I should look at (note that the client is non technical and I have no access to his machine).

Using numpy with "/arch nosse" solved the issue.

Probably OT here, but does anyone know if numpy will in the future be able to dynamically switch on/off the SSEx support?

Werner

···

On 18/02/2010 17:31, Werner F. Bruhin wrote:

On 18/02/2010 15:12, Werner F. Bruhin wrote:
   

Hi Everyone,

On 08/10/2009 06:54, Ross.Wilson@...2808... wrote:

Hi Listers,

I recently installed matplotlib 0.99.1 hoping to use mplot3d. However, when doing 'from mpl_toolkits.mplot3d import Axes3D' python itself crashes. Reinstalling matplotlib 0.98.5 gets everything working fine, without mplot3d, of course.

I am running Windows XP, python 2.5.2 and numpy 1.2.1. From the installation instructions I think I have all the prerequisites.

Has anyone seen behaviour like this?

It looks like I run into a similar issue on a client machine.

He is on Windows XP SP 2 Suisse edition and he gets "Unhandled
Exception" error which does not show any traceback.

My application is py2exe'd, so I did another build using 0.98.5 (both
with numpy 1.3, Python 2.5.4 and wxPython 2.8.10) but now at least we
get a traceback:

Traceback (most recent call last):
     File "appwine.pyo", line 939, in OnToolbarChart
     File "zipextimporter.pyo", line 82, in load_module
     File "frameplotmpl.pyo", line 24, in<module>
ImportError: cannot import name FigureCanvasWxAgg

The relevant section of frameplotmpl.py is:
from numpy import arange, sin, pi
import matplotlib as mpl
# following is already done on stats page
##mpl.use('WXAgg')
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx
from matplotlib.dates import YearLocator, MonthLocator, DateFormatter
from matplotlib.ticker import FormatStrFormatter
from matplotlib.font_manager import FontProperties

What is really strange I can run the same .exe on my XP test machine which is running XP SP2 English without any problems.

I know there is not much to go by here, but would very much appreciate if anyone has some hints/tips on what I should look at (note that the client is non technical and I have no access to his machine).

The user has an AMD CPU, could this be related to the numpy issue with
AMD machines?

Werner

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Werner F. Bruhin wrote:

Using numpy with "/arch nosse" solved the issue.

Probably OT here, but does anyone know if numpy will in the future be able to dynamically switch on/off the SSEx support?

not unless atlas grows that capability. atlas has to be built with particular features turned on or off at compile time.

Intel has a lapack that can dynamically select processors, but it's not open-source, and there are licensing issues to re-distributing it.

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@...259...

I am running again into crashes with matplotlib/numpy on Windows XP running on AMD Athlon type machiens.

I distribute the application with py2exe, so on my machine I install numpy with "/arch nosse".

This works on a test machine with my older program version which uses Python 2.5, matplotlib 0.99 and numpy 1.0.4, now with my newer stuff I use Python 2.6, still matplotlib 0.99 and numpy 1.3 (as there is no 1.0.4 for Py 2.6), with this configuration my program crashes on the Athlon CPU.

Tried upgrading to 1.4.1 and 1.5.1 of numpy (still using /arch nosse) but still see the same crash with an error code of "0xc000001d".

Short term a 1.0.4 for Python 2.6 would be an o.k. work around, but I really like to get a something better. Would an upgrade of matplotlib help?

Werner

···

On 18/02/2010 22:41, Werner F. Bruhin wrote:

Using numpy with "/arch nosse" solved the issue.

Probably OT here, but does anyone know if numpy will in the future be
able to dynamically switch on/off the SSEx support?

Hi
Werner

Using numpy with “/arch nosse” solved the issue.

Probably OT here, but does anyone know if numpy will in the future be

able to dynamically switch on/off the SSEx support?

I am running again into crashes with matplotlib/numpy on Windows XP

running on AMD Athlon type machiens.

I distribute the application with py2exe, so on my machine I install

numpy with “/arch nosse”.

This works on a test machine with my older program version which uses

Python 2.5, matplotlib 0.99 and numpy 1.0.4, now with my newer stuff I

use Python 2.6, still matplotlib 0.99 and numpy 1.3 (as there is no

1.0.4 for Py 2.6), with this configuration my program crashes on the

Athlon CPU.

Tried upgrading to 1.4.1 and 1.5.1 of numpy (still using /arch nosse)

but still see the same crash with an error code of “0xc000001d”.

Short term a 1.0.4 for Python 2.6 would be an o.k. work around, but I

really like to get a something better. Would an upgrade of matplotlib help?

Usually upgrading your software helps! :slight_smile:

···

Il giorno 18 aprile 2012 16:00, Werner F. Bruhin <werner.bruhin@…185…> ha scritto:

On 18/02/2010 22:41, Werner F. Bruhin wrote:

Werner


Better than sec? Nothing is better than sec when it comes to

monitoring Big Data applications. Try Boundary one-second

resolution app monitoring today. Free.

http://p.sf.net/sfu/Boundary-dev2dev


Matplotlib-users mailing list

Matplotlib-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-users


Cordiali saluti, Dr.Oteri Francesco

I think we have some confusion for version numbers. There was never a version 1.0.4 of mpl. There was a version 1.0.1, but not 1.0.4. Also, you mention numpy version 1.0.4, I certainly would hope you are referring to numpy 1.4.0. Could you please double-check your version numbers so we can get a better idea of what is happening?

Thanks,
Ben Root

···

On Wed, Apr 18, 2012 at 10:00 AM, Werner F. Bruhin <werner.bruhin@…185…> wrote:

On 18/02/2010 22:41, Werner F. Bruhin wrote:

Using numpy with “/arch nosse” solved the issue.

Probably OT here, but does anyone know if numpy will in the future be

able to dynamically switch on/off the SSEx support?

I am running again into crashes with matplotlib/numpy on Windows XP

running on AMD Athlon type machiens.

I distribute the application with py2exe, so on my machine I install

numpy with “/arch nosse”.

This works on a test machine with my older program version which uses

Python 2.5, matplotlib 0.99 and numpy 1.0.4, now with my newer stuff I

use Python 2.6, still matplotlib 0.99 and numpy 1.3 (as there is no

1.0.4 for Py 2.6), with this configuration my program crashes on the

Athlon CPU.

Tried upgrading to 1.4.1 and 1.5.1 of numpy (still using /arch nosse)

but still see the same crash with an error code of “0xc000001d”.

Short term a 1.0.4 for Python 2.6 would be an o.k. work around, but I

really like to get a something better. Would an upgrade of matplotlib help?

Werner

matplotlib-0.99.3.win32-py2.6 should work with numpy-1.4.1-win32-superpack-python2.6.exe

There was a bug prior to 0.99.2 (IIRC) that would crash on older Pentium computers.

If matplotlib-0.99.3 does crash with numpy-1.4.1, please send a small script and let us know exactly where and in which module it crashes, and the capabilities/model of your processor.

If possible, upgrade to numpy 1.6.1 and matplotlib 1.1.

Christoph

···

On 4/18/2012 7:00 AM, Werner F. Bruhin wrote:

On 18/02/2010 22:41, Werner F. Bruhin wrote:

Using numpy with "/arch nosse" solved the issue.

Probably OT here, but does anyone know if numpy will in the future be
able to dynamically switch on/off the SSEx support?

I am running again into crashes with matplotlib/numpy on Windows XP
running on AMD Athlon type machiens.

I distribute the application with py2exe, so on my machine I install
numpy with "/arch nosse".

This works on a test machine with my older program version which uses
Python 2.5, matplotlib 0.99 and numpy 1.0.4, now with my newer stuff I
use Python 2.6, still matplotlib 0.99 and numpy 1.3 (as there is no
1.0.4 for Py 2.6), with this configuration my program crashes on the
Athlon CPU.

Tried upgrading to 1.4.1 and 1.5.1 of numpy (still using /arch nosse)
but still see the same crash with an error code of "0xc000001d".

Short term a 1.0.4 for Python 2.6 would be an o.k. work around, but I
really like to get a something better. Would an upgrade of matplotlib help?

Werner