Coming from melodic, I always enjoyed analyzing bag data using rqt_bag tool. Recently, I started a new project using ROS2 iron and also jazzy and I noticed that the rqt_bag tool is almost unusable for me, quite in contrast to the melodic version.
So it is neither small nor big. Using melodic rqt_bag I worked in the past on bags much much larger without any issues.
System: Intel i7-5600U 12GB RAM, Ubuntu 22.04
Symptoms are:
Even after the bag has loaded completely (indicated by the progress bar at the bottom), rqt_bag occupies the CPU 100% for a couple of minutes, then idles (only true for iron)
The red marker cannot be repositioned, it stays at the beginning of the bag
Sometimes (no obvious explanation why) the marker can be moved, but only moves after a delay of several seconds
Obviously, with these issues the tool is not usable.
Since I haven't found other people having similar issues, I am wondering whether there is something I am doing wrong here. Any advice would be highly appreciated.
Hi
Coming from melodic, I always enjoyed analyzing bag data using rqt_bag tool. Recently, I started a new project using ROS2 iron and also jazzy and I noticed that the rqt_bag tool is almost unusable for me, quite in contrast to the melodic version.
Situation:
A bag in either sqlite or MCAP format
Contents:
So it is neither small nor big. Using melodic rqt_bag I worked in the past on bags much much larger without any issues.
System: Intel i7-5600U 12GB RAM, Ubuntu 22.04
Symptoms are:
Obviously, with these issues the tool is not usable.
Since I haven't found other people having similar issues, I am wondering whether there is something I am doing wrong here. Any advice would be highly appreciated.