-
Notifications
You must be signed in to change notification settings - Fork 69
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
segfault via rqt_pr2_dashboard #41
Comments
The one we were looking at was an illegal instruction but we did see a segfault as well during the testing that we could not pin down. |
This was happening pretty frequently when pointed at PRK, which is currently having motor trouble.
|
Similar trace with more debug symbols installed.
|
I changed the title of the issue since I can't confirm with rqt_robot_monitor standalone. I kept rqt_robot_monitor running all night with rqt 8b22c21 but didn't happen, whereas with rqt_p2_dashboard it occurs often. @ablasdel will look into rqt_robot_dashboard that's also used from rqt_p2_dashboard. |
My particular crash only appears to be happening with pyside bindings; it hasn't happened yet with pyqt. |
That is interesting. It looks like it must be robot monitor related because Could you please use both the pr2dashboard and in another instance have On Dec 7, 2012, at 13:43, Austin notifications@github.com wrote: My particular crash only appears to be happening with pyside bindings; it — |
Closing this for now, since I've been testing this for awhile by running 2 rqt_gui instances (1 runs rqt_robot_monitor and the other runs rqt_pr2_dashboard) and no error occurred last 10+ hours. Tested with |
With pyside segfaults has not occurred so far for several hours. |
After repeating enable-disable rqt_robot_monitor many (more than several dozens of) times on rqt_pr2_dashboard, rqt_gui segfaults.
Happens on @ablasdel's machine, but does not on mine (kept clicking for 5+ minutes x 2 times).
My environment:
ros-groovy-pr2-power-drivers/precise uptodate 1.0.9-s1354565896~precise
rqt commit 9eb8faa
To @dirk-thomas, @ablasdel
I even commented out graveyard but no difference.
The text was updated successfully, but these errors were encountered: