-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
pcl::MeshQuadricDecimationVTK seg fault #967
Comments
Alright, I compiled VTK from source in DEBUG mode, and the error message is the following:
Line 1101 is the IF statement below:
I narrowed down to the pts[j] variable returning an Invalid Pointer. So as a quick "hack solution" I wrapped the for loop with an if statement that checks for the pointer validity:
This "solved" the problem for me, but it doesn't actually tackle why this->Mesh->GetCellPoints is never initializing the pointer on some edge case. Best, Felipe |
So this is a bug on vtk side, not ours? |
Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs. |
Oi,
I am running a continuous loop that get the latest point-cloud from a laser sensor and transform it into a mesh.
The Point-cloud( input data) is very similar in each loop.
I am using the pcl::MeshQuadricDecimationVTK to decimate most of the mesh.
The code works for a few loops, behaving exactly like expected, but after what appears to be a random number of iterations it seg-faults with the following ( from gbd):
Program received signal SIGSEGV, Segmentation fault.
The specific lines in my code are =
For reference, the mesh generation from Point-Cloud is:
The computer is concurrently running a simulator, which hogs a lot of the memory. I am guessing this is an internal memory-leak. I wasn't able to find any similar bugs on the Issue Tracker
Any ideas? And is there any alternative options for the same functionality as MeshQuadricDecimationVTK?
Thanks in advance!
Felipe
The text was updated successfully, but these errors were encountered: