Runaway memory usage using HXT algorithm with size fields
I recently upgraded to gmsh 4.6.0, and I believe I have encountered a bug with respect to using size fields with the HXT algorithm.
When trying to mesh any geometry with the mesh size set via size fields, when using the the HXT algorithm memory usage would increase with every 3d Delauney step until the machine was out of memory. For the same geometries, I can switch the meshing algorithm to del3d
, and the mesh is successfully built. This memory bug did not occur with gmsh 4.5.6.
Attached is a reproduction example as well as a log file from a failed HXT build. The geometry is specified in geometry.brep, the meshing information is specified in geometry.geo_unrolled, and the resulting output log is gmsh_output.log.
For reference, gmsh
was obtained via conda using the conda-forge channel, and underlying OS was linux (reproduced on both CentOS and Debian). The hxt build command was:
gmsh -3 geometry.geo_unrolled -log gmsh_output.log -algo del2d -algo hxt -o geometry.msh -format msh2
and the del3d
build command was:
gmsh -3 geometry.geo_unrolled -log gmsh_output.log -algo del2d -algo del3d -o geometry.msh -format msh2