MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013978ParaView(No Category)public2013-03-28 17:352016-08-12 09:59
ReporterAlan Scott 
Assigned ToDave DeMarle 
PriorityhighSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Versiongit-master 
Target VersionFixed in Version 
ProjectSandia
Topic Name
Typecrash
Summary0013978: xdmf -binary files crashes with 7 time steps or more.
DescriptionWhen I wrap xdmf around numerous time variable binary files, ParaView crashes when deleting this file.

Linux, local server, master (and 3.98.1). Test dataset is one I voodoo'd up. It basically has 8 4 byte floats that are 0 (i.e., 0x00000000). Dataset is attached, and is called stl-timestep-crash.
* Open crash-opening-seven.xmf.
* Delete crash-opening-seven.xmf.
It will crash.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filesgz stl-timestep-crash.tar.gz (885) 2013-03-28 17:35
https://www.vtk.org/Bug/file/9426/stl-timestep-crash.tar.gz
Issue History
Date ModifiedUsernameFieldChange
2013-03-28 17:35Alan ScottNew Issue
2013-03-28 17:35Alan ScottFile Added: stl-timestep-crash.tar.gz
2013-04-30 15:34Sebastien JourdainAssigned To => Sebastien Jourdain
2013-04-30 15:34Sebastien JourdainStatusbacklog => todo
2013-04-30 15:34Sebastien JourdainStatustodo => active development
2013-04-30 15:44Sebastien JourdainNote Added: 0030637
2013-04-30 15:44Sebastien JourdainAssigned ToSebastien Jourdain => Utkarsh Ayachit
2013-04-30 15:45Sebastien JourdainStatusactive development => todo
2013-05-09 09:50Utkarsh AyachitNote Added: 0030734
2013-09-12 14:45Utkarsh AyachitAssigned ToUtkarsh Ayachit => Dave DeMarle
2013-09-12 14:46Utkarsh AyachitNote Added: 0031565
2016-08-12 09:59Kitware RobotNote Added: 0038373
2016-08-12 09:59Kitware RobotStatustodo => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved

Notes
(0030637)
Sebastien Jourdain   
2013-04-30 15:44   
Didn't manage to reproduce the crash more than once...
Hence I let it to Utkarsh on its Linux computer.
(0030734)
Utkarsh Ayachit   
2013-05-09 09:50   
Seems to be a Xdmf bug. Here's the invalid write call-stack that causes issues on delete.

==18297== Invalid write of size 4
==18297== at 0x2A0F01E8: void XdmfArrayCopy<float, double>(float*, long long, double*, long long, int, long long) (XdmfArrayCopyMacro.h:41)
==18297== by 0x2A0E927A: XdmfArray::SetValues(long long, char const*, long long, long long) (XdmfArray.cxx:604)
==18297== by 0x2A0FCA2F: XdmfValuesXML::Read(XdmfArray*) (XdmfValuesXML.cxx:53)
==18297== by 0x2A10BA70: XdmfDataItem::Update() (XdmfDataItem.cxx:539)
==18297== by 0x2A1203C9: XdmfTime::UpdateInformation() (XdmfTime.cxx:108)
==18297== by 0x2A11A412: XdmfGrid::UpdateInformation() (XdmfGrid.cxx:435)
==18297== by 0x1E835535: vtkXdmfDomain::vtkXdmfDomain(XdmfDOM*, int) (vtkXdmfReaderInternal.cxx:227)
==18297== by 0x1E83519E: vtkXdmfDocument::SetActiveDomain(int) (vtkXdmfReaderInternal.cxx:178)
==18297== by 0x1E82912A: vtkXdmfReader::PrepareDocument() (vtkXdmfReader.cxx:216)
==18297== by 0x1E8292B4: vtkXdmfReader::RequestDataObject(vtkInformationVector*) (vtkXdmfReader.cxx:233)
==18297== by 0x1E8287DF: vtkXdmfReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkXdmfReader.cxx:144)
(0031565)
Utkarsh Ayachit   
2013-09-12 14:46   
Assigning to Dave to test after the Xdmf reader has been updated to Xdmf 3.0.
(0038373)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.