Ticket #8460 (verify: worksforme)

Opened 7 years ago

Last modified 5 years ago

VSI Crash on Splatter Plot

Reported by: Owen Arnold Owned by: Federico M Pouzols
Priority: blocker Milestone: Backlog
Component: GUI Keywords:
Cc: Blocked By:
Blocking: Tester:


This is happening consistently on OSX 10.8. I haven't tried other platforms.

  • Load the SEQ_MDEW.nxs file in the Data directory of scripts in MantidPlot
  • Open the VSI in MantidPlot using this workspace
  • Rebin the workspace in the View (use defaults)
  • Delete the Rebinning filter out of the pipeline model (you are now back with original data source)
  • Hit the Splatter Plot button -> Crash

Change History

comment:1 Changed 7 years ago by Owen Arnold

Here's the stack trace

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libMantidVatesAPI.dylib       	0x0000000120539b7c void Mantid::VATES::vtkSplatterPlotFactory::doCreate<Mantid::MDEvents::MDEvent<4ul>, 4ul>(Mantid::MDEvents::MDEventWorkspace<Mantid::MDEvents::MDEvent<4ul>, 4ul>::sptr) const + 1132
1   libMantidVatesAPI.dylib       	0x00000001205272ab Mantid::VATES::vtkSplatterPlotFactory::create(Mantid::VATES::ProgressAction&) const + 1115
2   libMantidParaViewSplatterPlotSMPlugin.dylib	0x000000012f08dcab vtkSplatterPlot::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 363
3   libvtkCommonExecutionModel-pv3.98.1.dylib	0x0000000126eaa6b2 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 66
4   libvtkCommonExecutionModel-pv3.98.1.dylib	0x0000000126ea1b9d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 61
5   libvtkCommonExecutionModel-pv3.98.1.dylib	0x0000000126e9bef8 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 360
6   libvtkCommonExecutionModel-pv3.98.1.dylib	0x0000000126ea12f7 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1383
7   libvtkCommonExecutionModel-pv3.98.1.dylib	0x0000000126ebcd45 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1477
8   libvtkCommonExecutionModel-pv3.98.1.dylib	0x0000000126e9ccf3 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 

comment:2 Changed 7 years ago by Michael Reuter

I've tracked this issue down to a problem in ParaView. We have two sources that modify time steps (MD and rebinner) and their system doesn't quite handle that gracefully. I've posted something to the list, but no solution has been found. This may need to go on a contract to get done.

comment:3 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:4 Changed 5 years ago by Federico M Pouzols

  • Owner changed from Michael Reuter to Federico M Pouzols
  • Status changed from assigned to verify
  • Resolution set to worksforme

I think that this ticket has become obsolete? See #6407.

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 9304

Note: See TracTickets for help on using tickets.