Ticket #9083 (closed: wontfix)

Opened 7 years ago

Last modified 5 years ago

MantidPlot Crash with matplotlib

Reported by: Owen Arnold Owned by: Martyn Gigg
Priority: critical Milestone: Release 3.2
Component: Python Keywords:
Cc: Blocked By:
Blocking: Tester: Michael Reuter

Description

Quote from Tim Charlton

Also I found that running a plt.show() from matplotlib crashes mantidplot. I had a similar experience running with only an ipython shell.  In this case the shell either dies or restarts.

Change History

comment:1 Changed 7 years ago by Owen Arnold

  • Component changed from Framework to Python API

comment:2 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned
  • Owner changed from Anyone to Martyn Gigg

Martyn, can you give this a quick test

comment:3 Changed 7 years ago by Martyn Gigg

  • Status changed from assigned to verify
  • Resolution set to wontfix

This is a known issue with the current single-process asynchronous python scripts. There is a workaround that is described here: http://www.mantidproject.org/MantidPlot:External_Python_Plotting_Package

comment:4 Changed 7 years ago by Michael Reuter

Using the second example on the given link, I get the following error (no crash):

TypeError: threadsafe_call() got an unexpected keyword argument 'color'
  at line 5 in '/home/2zr/mscripts/test_matplotlib.py'

and no plot appears.

comment:5 Changed 7 years ago by Michael Reuter

  • Status changed from verify to verifying
  • Tester set to Michael Reuter

comment:6 Changed 7 years ago by Michael Reuter

I'm making the executive decision that in spite of the above error, this doesn't cause Mantid to crash. However, keywords cause the command to fail and not produce a plot which is a problem. So, I'm creating another ticket to address this.

comment:7 Changed 7 years ago by Michael Reuter

  • Status changed from verifying to closed

OK, I've created #9092 to address this.

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 9926

Note: See TracTickets for help on using tickets.