-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: double free errors #10
Comments
Was built on
|
This may be related to the poisson reconstruction python binding interface mmolero/pypoisson#13 |
@tylerjereddy , thanks for opening the issue and @ctlee , thanks for connecting it with the pypoisson issue. There appears to be a memory bug in the original code for python reconstruction that slips through the cracks in older compilers, but it appears that gcc>8 is not letting it through. I spent quite some time digging down the cause, and I suspect really fixing it requires an overhaul of the original cpp code (see my comment here.) Until then, I tried the code again with I will leave this issue open but add to ReadMe the need to stick with |
Probably there should never be
double free
C++ errors, regardless of the input data, if the memory handling is safe throughout the library and its dependency stack.Here is a reproducer using nothing more than NumPy,
pytest
, and thehypothesis[numpy]
property-based testing library:Run the test below with version
1.0
ofmemsurfer
with:pytest reproducer.py -s
It will hard crash:
The text was updated successfully, but these errors were encountered: