Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,672
    • Issues 1,672
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 59
    • Merge Requests 59
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #20447

Closed
Open
Created Jan 25, 2021 by Kenneth Moreland@kmorelDeveloper

File Open can cause ParaView to crash when invalid volume mounted

Multiple users have reported that ParaView crashes immediately on mac after clicking on File -> Open. The crash happens before the file browser appears, so it has nothing to do with a malformed file. Here are two references to such a problem:

  • https://www.paraview.org/pipermail/paraview/2017-March/039781.html
  • https://discourse.paraview.org/t/paraview-crashes-immediately-when-opened/6278

In both cases, the problem appeared to be an issue with the system having mounted a volume that cannot be accessed. One of the users reported that running ls -l /Volumes caused the error ls: volume_name: Permission denied to occur. Unmounting the inaccessible volume seems to fix the problem with ParaView.

ParaView seems to be crashing when it is not able to access mounted volumes (probably when it is collecting the "special" directories). ParaView should instead either issue a warning or just ignore the directory.

This might be related to #17536, which appears to be a similar problem on Windows.

A workaround to this problem is to unmount any file system that you don't have access to.

Edited Jan 25, 2021 by Kenneth Moreland
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None