Ticket #4988 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Segmentation fault in VSI SplatterPlot overplot

Reported by: Andrei Savici Owned by: Michael Reuter
Priority: major Milestone: Release 2.1
Component: VATES Keywords:
Cc: Blocked By:
Blocking: Tester: Owen Arnold

Description (last modified by Michael Reuter) (diff)

The SplatterPlot mode should not allow more than one MDWorkspace to be viewed while the mode is active. When trying to overplot, this causes a segmentation fault.

Change History

comment:1 Changed 9 years ago by Michael Reuter

Can you give me a specific example? I've just tried two different test cases and it works for me.

comment:2 Changed 9 years ago by Michael Reuter

  • Status changed from new to accepted
  • Description modified (diff)
  • Summary changed from Segmentation fault in Vates Simple when overploting to Segmentation fault in VSI SplatterPlot overplot

comment:3 Changed 9 years ago by Michael Reuter

Refs #4988. Disallow more than one MDWorkspace on SplatterPlot.

Changeset: 4d1f96f461b82f8ebe8a7ad37ecd04aff6f8619c

comment:4 Changed 9 years ago by Michael Reuter

  • Status changed from accepted to verify
  • Resolution set to fixed

To test, load the TOPAZ_3680_5_sec_MDEW.nxs file into MantidPlot and the view in the VSI, Next switch to SplatterPlot mode. Then try to load the MD workspace again into the VSI. You should get a warning dialog and the program should not crash.

comment:5 Changed 9 years ago by Michael Reuter

Refs #4988. Disallow more than one MDWorkspace on SplatterPlot.

Changeset: 4d1f96f461b82f8ebe8a7ad37ecd04aff6f8619c

comment:6 Changed 8 years ago by Owen Arnold

  • Status changed from verify to verifying
  • Tester set to Owen Arnold

comment:7 Changed 8 years ago by Owen Arnold

  • Status changed from verifying to closed

Good. Received warning message about this.

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​5834

Note: See TracTickets for help on using tickets.