-
Notifications
You must be signed in to change notification settings - Fork 20
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] Memory issues when using the solver for multiple registration attempts #30
Comments
Oh thanks for reporting! Hmm...that looks off, but occasionally, I also saw that error. Could you run the code like this?
|
In the case of Python, at which iteration does the error occur? |
Hmmm...bro I tested python by running KISS-Matcher multiple time; but there are no memory issues. Could you check your data carefully? Because you acquired very noisy data, right? Or if it is possible, you can share your python script and data with me. |
My bad, apparently it's happening also with the "pure" cpp code, at least there is one less layer (pybinding) to worry about. Just in case here is a video proving I'm not going mad: https://drive.google.com/file/d/1V_3Un0wdeE0gZWq2ECEtALP-G2xTMjde/view?usp=sharing |
Hi!
first of all: I don't know if this is a bug or if I'm not doing something properly.
I need to use the KISS matcher to align multiple pointclouds, like in a loop, but after a couple hundreds of alignments I get the error
This is a snippet to reproduce my error, I took the
examples/run_kiss_matcher.py
script and instead of solving the registration one time I do it in a loop for a thousand times. After a non-deterministic amout of iterations I get the error copied above.Snippet:
As show above, I'm clearing and resetting the matcher object, but maybe it is not enough to completely clear the internal state?
I tried to do the same thing in cpp and apparently there is no memory bug there, so I guess it has something to do with the pybiding. I tried to search in the pybinding repo issues and there are other people complaining about similar problems, but I haven't been able to pinpoint what exactly is making the python script crash.
The text was updated successfully, but these errors were encountered: