Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #17129
Closed
Open
Issue created Jan 23, 2017 by John Patchett@patchett2002Developer

pvtu segfaults when read into ParaView and then deleted

A pvtu file produced from a ParaView workflow, "saving data" after a threshold (attached) causes many ParaView 5.2.0 s to segfault when the pvtu is read and then the source is deleted. The pvtu file that is attached has only 2 vtu files, but an entire series was produced and they all seem to cause this problem. The segfault is on the server side. The bug has been replicated with both intel and gcc compilers on two different compute clusters. The problem is also seen on a serial linux implementation: both binaries from paraview.org and locally built source.
ParaView 5.2.0 binaries for Mac OSX on a 10.11.6 el capitan machine DOES NOT reproduce the problem. Not tested on Windows. The attached files have zlib compression, the problem was also observed with intel compiler with parallel produced pvtu with no compression.

AsteroidOnly.tar

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking