Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 47
    • Merge requests 47
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #129

Closed
Open
Created Jan 25, 2022 by Bruce Joseph Gallop@bgallopMaintainer

RawData memory management

As raised in !340 (merged), the RawData class doesn't handle it's own memory, but handles raw pointers.

When used in combination with RawDataContainer, this works as intended, but in the cases where this isn't used (mostly test cases, but also some standalone apps), the memory has to be deleted manually.

So the question is whether there's an easy way of modernising this. Would switching to unique_ptr make sense, or does that break in conjunction with RawDataContainer.

Alternatively, should this instead be switched to using something like arenas for managing repeated allocations better.

(I have a feeling this is raised somewhere else, if someone can find another issue to link to)

Assignee
Assign to
Time tracking