Skip to content
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 in World->removeSkeleton() #330

Closed
ana-GT opened this issue Feb 11, 2015 · 2 comments
Closed

Bug in World->removeSkeleton() #330

ana-GT opened this issue Feb 11, 2015 · 2 comments
Assignees
Labels
priority: high should be resolved right now type: bug Indicates an unexpected problem or unintended behavior
Milestone

Comments

@ana-GT
Copy link
Collaborator

ana-GT commented Feb 11, 2015

Hi, here a report on the following bug:

Function: removeSkeleton()
Location: dart/simulation/World.cpp (line 246)
Error: The function should delete the skeleton name from the mNameMgrForSkeletons, which is not currently being done.
Fix: Add the following 2 lines probably after line 265 for safe checks:

// Remove from name manager
mNameMgrForSkeletons.removeName( _skeleton->getName() );

I am using a program in which I constantly add/delete skeletons with the same name for some online object detection. I was getting SEGFAULTS after deleting an skeleton and then trying to add it later (the NameManager thought the object still existed, but the Skeleton had been already erased).

After adding the couple of lines mentioned above, the issue dissapared.

@mxgrey
Copy link
Member

mxgrey commented Feb 11, 2015

Good catch. I'll throw in a fix immediately, and make a regression test for
this.
On Feb 11, 2015 1:42 PM, "Ana" notifications@github.com wrote:

Hi, here a report on the following bug:

Function: removeSkeleton()
Location: dart/simulation/World.cpp (line 246)
Error: The function should delete the skeleton name from the
mNameMgrForSkeletons, which is not currently being done.
Fix: Add the following 2 lines probably after line 265 for safe checks:

// Remove from name manager
mNameMgrForSkeletons.removeName( _skeleton->getName() );

I am using a program in which I constantly add/delete skeletons with the
same name for some online object detection. I was getting SEGFAULTS after
deleting an skeleton and then trying to add it later (the NameManager
thought the object still existed, but the Skeleton had been already
erased).

After adding the couple of lines mentioned above, the issue dissapared.


Reply to this email directly or view it on GitHub
#330.

@mxgrey
Copy link
Member

mxgrey commented Feb 11, 2015

Pull request #331 now addresses this issue.

@mxgrey mxgrey added type: bug Indicates an unexpected problem or unintended behavior priority: high should be resolved right now labels Feb 12, 2015
@mxgrey mxgrey self-assigned this Feb 12, 2015
@mxgrey mxgrey closed this as completed Feb 14, 2015
@jslee02 jslee02 added this to the Release DART 5.0 milestone Feb 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high should be resolved right now type: bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants