Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gmsh
gmsh
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 107
    • Issues 107
    • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gmsh
  • gmshgmsh
  • Merge Requests
  • !236

Open
Opened Feb 08, 2019 by Wendy Merks-Swolfs@ws_plaxisDeveloper
  • Report abuse
Report abuse

Prevent some endless loops in Tetgen by taking counter into account and...

  • Overview 2
  • Commits 1
  • Pipelines 1
  • Changes 1

Prevent some endless loops in Tetgen by taking counter into account and terminate if the value of the counter becomes too high. We've experienced within our testsuite the maximum value encountered for the counter and now terminate when the counter becomes much higher than this maximum value.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: gmsh/gmsh!236
Source branch: PreventEndlessLoopsTetgen