Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenFlipper-Free
OpenFlipper-Free
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • OpenFlipper-Free
  • OpenFlipper-FreeOpenFlipper-Free
  • Issues
  • #143

Closed
Open
Opened 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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: OpenFlipper-Free/OpenFlipper-Free#143