MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011762ParaViewBugpublic2011-01-26 03:492016-08-12 09:58
ReporterJens Kleimann 
Assigned ToKitware Robot 
PriorityhighSeveritycrashReproducibilityalways
StatusclosedResolutionmoved 
PlatformLinuxOSLinuxOS Version2.6.32-5-amd64
Product Version3.8.1 
Target VersionFixed in Version 
Project
Topic Name
Type
Summary0011762: Xdmf file with hyperslab itemtype crashes Paraview
DescriptionThe attached file, which is supposed to cut a 2x2x2 cube out of a larger 3x3x3 cube, causes Paraview to crash. ("*** glibc detected *** ... realloc(): invalid next size: 0x0000000008e1a800 ***")
To extract the subgrid [0,1]^3 from the larger [0,2]^3 grid, the start-stride-count in the first DataItem is set to
 0 0 0
 1 1 1
 2 2 2
The same behavior occurs when trying to access the opposite corner [1,2]^3 (the one with values in the [8,15] range) using
 1 1 1
 1 1 1
 2 2 2
instead. The crash can apparently be avoided using ranges whose count values are at least 3 (which should obviously be too large for the 2x2x2 target grid), and even grossly out-of-bound values such as
 12 11 321
 1 1 1
 6 13 13
are accepted without complaints, and result in
 1 2 0 3 4 0 0 0
i.e. a copy of the beginning of the source array.
Steps To ReproduceOpen Paraview, File->Open attached file "hyperslab_test.xmf", hit Apply.
Additional InformationI have also reported this prospective bug to Project Xdmf because it is unclear on which side the problem is.
TagsNo tags attached.
Relationships
Attached Files? hyperslab_test.xmf (1,395) 2011-01-26 03:49
https://www.vtk.org/Bug/file/8658/hyperslab_test.xmf
Issue History
Date ModifiedUsernameFieldChange
2011-01-26 03:49Jens KleimannNew Issue
2011-01-26 03:49Jens KleimannFile Added: hyperslab_test.xmf
2016-08-12 09:58Kitware RobotNote Added: 0037913
2016-08-12 09:58Kitware RobotStatusbacklog => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved
2016-08-12 09:58Kitware RobotAssigned To => Kitware Robot

Notes
(0037913)
Kitware Robot   
2016-08-12 09:58   
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.