Zhang Jinyang

@kingToolbox double-click Xming.exe, XMing.exe can run normally. but ten seconds later, it disappears from task manager. what's wrong?

@bennydente I encontered the same issue, so what's the resolution?

我现在用的是付费API，依然出现这种情况 

But if I test with the Docker image arm64v8/ros:humble-ros-core, the CPU usage is normal. Could it be because there's an issue with the versions of rclpy libraries I compiled? 

> > Nvidia Jetson Xavier NX, Ubuntu 18.04 > > Are you running the container image on top of this host system? container image > > > rclpy(Foxy): 1.0.13 >...

This is my dockerfile: ``` FROM nvcr.io/nvidia/l4t-base:r32.5.0 ENV OPENBLAS_CORETYPE=ARMV8 ENV PYTHONDONTWRITEBYTECODE=1 ENV PYTHONUNBUFFERED=1 ENV RMW_IMPLEMENTATION=rmw_cyclonedds_cpp ARG DEBIAN_FRONTEND=noninteractive ARG TOOLS=" \ build-essential \ fish \ sudo \ git \ vim \...

If I compile the ROS Humble on Ubuntu 22.04, the CPU usage returns to the same level as Foxy. But it still remains higher than `arm64v8/ros:humble-ros-core`. 

any advice ?

@fujitatomoya Through an open-source analysis tool, [VizTracer ](https://github.com/gaogaotiantian/viztracer)library, I discovered that within each `spin_once` iteration, the `add_node` function in the Humble takes longer compared to Foxy. Subsequently, when I commented...

Why is add_node called first in each spin_once iteration, followed by remove_node? Can using `StaticSingleThreadedExecutor` help avoid this situation?