-
Notifications
You must be signed in to change notification settings - Fork 466
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
Unhandled exception when marker contains mesh from unknown package #1589
Comments
Thanks. |
Strange one ... I also couldn't reproduce it in standalone rviz but it successfully crashes our UI that includes the The crash also happens in comparing rviz and the embedded use case I see that rviz prints out the following for every marker, interactive marker, robot:
while rviz embedded in our application only prints that for
Here is another backtrace:
I'm not sure how to debug this further and have some headache due to covid so I'd be grateful for ideas. I noticed that |
I might have an idea: Do you load the same mesh, both with rviz/src/rviz/robot/robot_link.cpp Lines 596 to 600 in 13d061d
and thus creates an invalid entity. Next time when the resource is requested, this existing but invalid entity is returned: Lines 671 to 674 in 13d061d
|
Good catch @rhaschke ! Now I can crash rviz as well (by enabling a Not setting the entity in |
Do you see a more convenient way than adding a chain of signal/slots in |
No, I'm afraid that's the only way. I'm fine to merge #1596 as is. |
Closed via #1629. |
When a marker msgs with a mesh from an unknown package is loaded, it throws an Ogre exception which is unfortunately not handled:
Your environment
[ INFO] [1613475494.475289937]: compiled against Qt version 5.12.8
[ INFO] [1613475494.475299717]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1613475494.483962728]: Forcing OpenGl version 0.
[ INFO] [1613475495.046200133]: Stereo is NOT SUPPORTED
[ INFO] [1613475495.046340502]: OpenGl version: 3,0 (GLSL 1,3).
I'll try to provide a PR soon
The text was updated successfully, but these errors were encountered: