Fatal Python Error with 64 bit versions

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python, numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

···

--
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29392620.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Which version of numpy are you using? Assuming you are talking about matplotlib-1.0.0.win-amd64-py2.6.exe, you need numpy-1.4.1.win-amd64-py2.6.exe.

Christoph

···

On 8/9/2010 3:09 PM, stetrick wrote:

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python, numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

Christoph Gohlke wrote:

···

On 8/9/2010 3:09 PM, stetrick wrote:

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python,
numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

Using Numpy 1.4.1 on Windows 7 64 bit.
Python version 2.6.5 for 64 bit as well. All from your website of
pre-compiled stuff.

Thanks for doing that!

Which version of numpy are you using? Assuming you are talking about
matplotlib-1.0.0.win-amd64-py2.6.exe, you need
numpy-1.4.1.win-amd64-py2.6.exe.

Christoph

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

--
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29401026.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Should probably indicate that it is the MKV versions

stetrick wrote:

···

Christoph Gohlke wrote:

On 8/9/2010 3:09 PM, stetrick wrote:

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python,
numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

Using Numpy 1.4.1 on Windows 7 64 bit.
Python version 2.6.5 for 64 bit as well. All from your website of
pre-compiled stuff.

Thanks for doing that!

Which version of numpy are you using? Assuming you are talking about
matplotlib-1.0.0.win-amd64-py2.6.exe, you need
numpy-1.4.1.win-amd64-py2.6.exe.

Christoph

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

--
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29401038.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Those versions should work. Can you post some more details how you run python and a script that shows this problem. I assume you can import and use matplotlib and the crash appears when exiting Python? It might just be the old known bug in the Tk backend, not anything specific to the 64 bit version. See <http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/msg15342.html>

···

On 8/10/2010 11:53 AM, stetrick wrote:

Should probably indicate that it is the MKV versions

stetrick wrote:

Christoph Gohlke wrote:

On 8/9/2010 3:09 PM, stetrick wrote:

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python,
numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

Using Numpy 1.4.1 on Windows 7 64 bit.
Python version 2.6.5 for 64 bit as well. All from your website of
pre-compiled stuff.

Thanks for doing that!

--
Christoph

I thought that was fixed:
http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720

Eric

···

On 08/10/2010 09:10 AM, Christoph Gohlke wrote:

On 8/10/2010 11:53 AM, stetrick wrote:

Should probably indicate that it is the MKV versions

stetrick wrote:

Christoph Gohlke wrote:

On 8/9/2010 3:09 PM, stetrick wrote:

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python,
numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

Using Numpy 1.4.1 on Windows 7 64 bit.
Python version 2.6.5 for 64 bit as well. All from your website of
pre-compiled stuff.

Thanks for doing that!

Those versions should work. Can you post some more details how you run
python and a script that shows this problem. I assume you can import and
use matplotlib and the crash appears when exiting Python? It might just
be the old known bug in the Tk backend, not anything specific to the 64
bit version. See
<http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/msg15342.html>

--
Christoph

Yes the bug is fixed. If the program is terminated properly. However, you can still crash the Python interpreter if you close or kill the console window while the following script is running.

python -c"from matplotlib import pyplot;pyplot.hot();input()"

···

On 8/10/2010 12:26 PM, Eric Firing wrote:

On 08/10/2010 09:10 AM, Christoph Gohlke wrote:

On 8/10/2010 11:53 AM, stetrick wrote:

Should probably indicate that it is the MKV versions

stetrick wrote:

Christoph Gohlke wrote:

On 8/9/2010 3:09 PM, stetrick wrote:

I am now getting a message that says:

Fatal Python error: PyEval_RestoreThread: NULL tstate

This application has requested the Runtime to terminate it in an unusual
way.

This is with matplotlib 1.0.0, but all versions are 64-bit (python,
numpy,
matplotlib).

Is this something I can fix or ignore?

Thanks!

Using Numpy 1.4.1 on Windows 7 64 bit.
Python version 2.6.5 for 64 bit as well. All from your website of
pre-compiled stuff.

Thanks for doing that!

Those versions should work. Can you post some more details how you run
python and a script that shows this problem. I assume you can import and
use matplotlib and the crash appears when exiting Python? It might just
be the old known bug in the Tk backend, not anything specific to the 64
bit version. See
<http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/msg15342.html>

--
Christoph

I thought that was fixed:
http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720

Eric

--
Christoph

I removed and reinstalled everything, and I'm still getting it.

I am using the multiprocessing lib. Each process then produces a graph with
matplotlib, which is only done with Savefig (never interactively displaced
during the creation process). I have nothing special in the configuration
- just using the 64-bit windows defaults.

Probably some setup thing.

Christoph Gohlke wrote:

···

Christoph

I thought that was fixed:
http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720

Eric

Yes the bug is fixed. If the program is terminated properly. However,
you can still crash the Python interpreter if you close or kill the
console window while the following script is running.

python -c"from matplotlib import pyplot;pyplot.hot();input()"

--
Christoph

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

--
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413051.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Adding a close() at the end didn't do anything - still get the same message.

stetrick wrote:

···

I removed and reinstalled everything, and I'm still getting it.

I am using the multiprocessing lib. Each process then produces a graph
with matplotlib, which is only done with Savefig (never interactively
displaced during the creation process). I have nothing special in the
configuration - just using the 64-bit windows defaults.

Probably some setup thing.

Christoph Gohlke wrote:

Christoph

I thought that was fixed:
http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720

Eric

Yes the bug is fixed. If the program is terminated properly. However,
you can still crash the Python interpreter if you close or kill the
console window while the following script is running.

python -c"from matplotlib import pyplot;pyplot.hot();input()"

--
Christoph

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

--
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413159.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Again, please post a complete script that can reproduce the problem. Since you do not need a GUI did you try to use the Agg backend?

Christoph

···

On 8/11/2010 2:31 PM, stetrick wrote:

I removed and reinstalled everything, and I'm still getting it.

I am using the multiprocessing lib. Each process then produces a graph with
matplotlib, which is only done with Savefig (never interactively displaced
during the creation process). I have nothing special in the configuration
- just using the 64-bit windows defaults.

Probably some setup thing.

Christoph Gohlke wrote:

Christoph

I thought that was fixed:
http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720

Eric

Yes the bug is fixed. If the program is terminated properly. However,
you can still crash the Python interpreter if you close or kill the
console window while the following script is running.

python -c"from matplotlib import pyplot;pyplot.hot();input()"

--
Christoph

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Setting the matplotlib.use('Agg') seems to have made the problem go away.

Thanks for your patience.
Scott

Christoph Gohlke wrote:

···

Again, please post a complete script that can reproduce the problem.
Since you do not need a GUI did you try to use the Agg backend?

Christoph

On 8/11/2010 2:31 PM, stetrick wrote:

I removed and reinstalled everything, and I'm still getting it.

I am using the multiprocessing lib. Each process then produces a graph
with
matplotlib, which is only done with Savefig (never interactively
displaced
during the creation process). I have nothing special in the
configuration
- just using the 64-bit windows defaults.

Probably some setup thing.

Christoph Gohlke wrote:

Christoph

I thought that was fixed:
http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720

Eric

Yes the bug is fixed. If the program is terminated properly. However,
you can still crash the Python interpreter if you close or kill the
console window while the following script is running.

python -c"from matplotlib import pyplot;pyplot.hot();input()"

--
Christoph

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

--
View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413496.html
Sent from the matplotlib - users mailing list archive at Nabble.com.