Skip to content

[humble] Fix for memory leaks in the rclcpp::SerializedMessage (backport #2861)#2865

Merged
ahcorde merged 1 commit intohumblefrom
mergify/bp/humble/pr-2861
May 30, 2025
Merged

[humble] Fix for memory leaks in the rclcpp::SerializedMessage (backport #2861)#2865
ahcorde merged 1 commit intohumblefrom
mergify/bp/humble/pr-2861

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented May 29, 2025

Description

This PR fixes memory leaks found in the rclcpp::SerializedMessage copy assignment operators

Fixes # (issue) N/A

Is this user-facing behavior change?

No

Did you use Generative AI?

No.

Additional Information

These memory leaks were found with memory sanitizer.


This is an automatic backport of pull request #2861 done by [Mergify](https://mergify.com).

Signed-off-by: Michael Orlov <morlovmr@gmail.com>
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
Co-authored-by: kylemarcey <marcey.kyle@gmail.com>
(cherry picked from commit 8d44b95)
@fujitatomoya
Copy link
Copy Markdown
Collaborator

Pulls: #2865
Gist: https://gist.githubusercontent.com/fujitatomoya/adfb60e8d4a38f50ea3692c7a6e9761f/raw/0b2c8f4455f0d7d4c50cfb59b711211c80e45220/ros2.repos
BUILD args: --packages-above-and-dependencies rclcpp
TEST args: --packages-above rclcpp
ROS Distro: humble
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/16115

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@MichaelOrlov MichaelOrlov changed the title Fix for memory leaks in the rclcpp::SerializedMessage (backport #2861) [humble] Fix for memory leaks in the rclcpp::SerializedMessage (backport #2861) May 29, 2025
@ahcorde ahcorde merged commit c4e82dd into humble May 30, 2025
2 of 3 checks passed
@ahcorde ahcorde deleted the mergify/bp/humble/pr-2861 branch May 30, 2025 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants