Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • OpenFlipper-Free OpenFlipper-Free
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenFlipper-FreeOpenFlipper-Free
  • OpenFlipper-FreeOpenFlipper-Free
  • Issues
  • #143
Closed
Open
Issue created Feb 05, 2018 by Martin Heistermann@mheistermannDeveloper

Copying Volume Mesh objects leads to memory corruption

The VolumeMeshObject copy constructor (used by its own copy() method) creates a second shared pointer to the actual mesh instead of copying the mesh.

Steps to crash:

  1. Create volume object
  2. Create a copy using DataControl
  3. Exit OF, observe crash
Edited Feb 05, 2018 by Martin Heistermann
Assignee
Assign to
Time tracking