Replicated component leak on clients if RPC forces construction and server destroys it in the same frame

RPCs called on actors force a channel to be opened and the actor to be replicated at least once. If the RPC is called on a new replicated component while the actor channel is already open, but the component is immediately destroyed after the RPC call, the RPC header will force the creation of the component on the client side, but the destruction header will never be written by the server because it will not be added to the channel's replication map.

1. Create a replicated component with a reliable RPC
2. On an actor with an existing channel (ie PlayerController), create the component, call the RPC, and destroy the component in the same frame
3. On the client note that the component is created, the RPC is called, but the component is never destroyed

How does TextureRenderTarget2D get TArray<uint8> type data?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

Why does the REMOVE method of map container remove elements have memory leaks?

How do I set a material as a post-processing material?

How to delete some elements correctly when deleting an array loop?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

UMG RichText not appear image when packaged

What is the difference between Camera and CineCamera?

How does TArray loop correctly remove elements in blueprints?