Fast winding number terminates with some meshes / segfaults

[mark-at-hypothetic]

Hi!
I'm using
fast_winding_number_for_meshes(v: array, f: array, q: array)
Mostly it works, but with some variations of v and f, the code crashes, and gives C++ errors without a clear stack trace. Just

terminate called without an active exception
terminate called recursively
terminate called recursively
[1]    697800 IOT instruction (core dumped)

q is of size 256x256x256x3
The problem is sporadic for different meshes, and haven't found what exactly triggers a crash, just that it's reproducible with the same mesh, and that this error doesn't happen when simplifying the mesh to have less vertices.

using python 3.10, and libigl 2.4.1

[alecjacobson]

Could you please upload the problematic input?

[guohaoxiang]

I met the same bugs. Here are the files and codes to reproduce this bug.

data link: https://drive.google.com/file/d/1K7r3udYOXrwn4kmWq--rvDquBkN49sGK/view?usp=sharing

def reproduce_bugs():
    m = trimesh.load('Maserati.obj')
    nonsurf_points = np.loadtxt('nonsurf_points.xyz')
    wn = igl.fast_winding_number_for_meshes(m.vertices, m.faces, nonsurf_points)

Note that the bug occurs occasionally. Every 3 or 4 times I run the program, the bug will occur.

[guohaoxiang]

By the way, I find I can reproduce this bug on a Ubuntu 22.04 machine with python 3.10.6, but I can not reproduce it on my windows machine with python 3.10.9