-
Notifications
You must be signed in to change notification settings - Fork 522
Closed
Description
Bug report
Required Info:
-
Operating System:
- Ubuntu 20.04
-
Installation type:
- binaries
-
Version or commit hash:
- 2.0.2
-
DDS implementation:
- Fast-RTPS
-
Client library (if applicable):
- rclcpp-lifecycle
Steps to reproduce issue
Run this node and start it using a life cycle manager.
#include <rclcpp/rclcpp.hpp>
#include <rclcpp_lifecycle/lifecycle_node.hpp>
using LifecycleCallbackReturn = rclcpp_lifecycle::node_interfaces::LifecycleNodeInterface::CallbackReturn;
class TestNode : public rclcpp_lifecycle::LifecycleNode
{
public:
explicit TestNode(const rclcpp::NodeOptions options)
: rclcpp_lifecycle::LifecycleNode("test_node", options)
{}
LifecycleCallbackReturn on_configure(const rclcpp_lifecycle::State&) { return LifecycleCallbackReturn::SUCCESS; }
LifecycleCallbackReturn on_activate(const rclcpp_lifecycle::State&)
{
auto node = std::make_shared<rclcpp::Node>("service_node");
return LifecycleCallbackReturn::SUCCESS;
}
LifecycleCallbackReturn on_deactivate(const rclcpp_lifecycle::State&) { return LifecycleCallbackReturn::SUCCESS; }
LifecycleCallbackReturn on_cleanup(const rclcpp_lifecycle::State&) { return LifecycleCallbackReturn::SUCCESS; }
LifecycleCallbackReturn on_shutdown(const rclcpp_lifecycle::State&) { return LifecycleCallbackReturn::SUCCESS; }
LifecycleCallbackReturn on_error(const rclcpp_lifecycle::State&) { return LifecycleCallbackReturn::SUCCESS; }
};
int main(int argc, char * argv[])
{
rclcpp::init(argc, argv);
rclcpp::executors::SingleThreadedExecutor exec;
rclcpp::NodeOptions options;
auto scheduler = std::make_shared<TestNode>(options);
exec.add_node(scheduler->get_node_base_interface());
exec.spin();
rclcpp::shutdown();
return 0;
}
Expected behavior
Node should start and activate after which CPU usage should get low.
Actual behavior
Node does start (The lifecycle manager indicates it succeeded and I have had this issue with a more complex node as well, which responded after starting) but the CPU usage remains around 100% (viewed using htop).
Additional information
Node creation is required to call a service in the on_activate
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
