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,962
    • Issues 1,962
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • 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
  • #19154
Closed
Open
Issue created Jul 03, 2019 by W. Alan Scott@wascottMaintainer

Exodus reader crash with superelements

We have a crash in an exodus dataset. This dataset has superelements.

  • 5.7.0-RC1, Linux, local server.
  • Open SAND2017-5827O-FSM_Residual-bad-eigen.e. ParaView will crash in the reader freeing memory that it doesn't own.

This dataset opens correctly with EnSight.

I will send two datasets to Utkarsh and Cory. Datasets are UUR.

  • SAND2017-5827O-FSM_Residual-bad-eigen.e
  • SAND2017-5827O-FSM_Residual-good-eigen.e
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking