Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 423
    • Issues 423
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #2300
Closed
Open
Issue created Dec 13, 2021 by Mark OLESEN@markMaintainer

odd behaviour with namedDictionary and/or SLList

Still under investigation - @Mattijs noticed that valgrind + topoSet was indicating some memory issues. v2012 is fine, v2106 and v2112 exhibit this problem. The main change between these versions is the handling of the topoSet entries. There were previously a PtrList of entry, which meant that naming the action (looks like a dictionary) would not work - the reading would grab the entire content as a dictionary instead.

The problem seems to lie either with some assignment problems with namedDictionary itself, or slicing of the SLList types. Changing the List to an SLList in the topoSet application seems to indicate it might be the latter.

Testing on simpleFoam/pipeCyclic

Will investigate after the v2112 release.

Edited Jan 12, 2022 by Mark OLESEN
Assignee
Assign to
Time tracking