IsTraceHandleValid with default FTraceHandles has unexpected behavior on the first frame

Because both FWorldAsyncTraceState's CurrentFrame and FTraceHandle are default initialized to 0, on the first frame, if a new Asnc Trace starts all default FTraceHandles will reference the same (now valid) data. This results in presumed distinct default FTraceHandles unexpectedly affecting the validity via IsTraceHandleValid of one another.

1. Setup 2 instances of an Actor with a default initialized FTraceHandle.
2. Have the actors check IsTraceHandleValid on this handle on the first frame. 
3. If invalid, replace with results from a new Async Trace.

Expected Results: Both actors receive invalid and create new traces.

Actual Results: The first actor receives invalid and creates a new trace, the second receives valid

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

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?

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

UMG RichText not appear image when packaged

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

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

What is the difference between Camera and CineCamera?

What controls of umg have mouse wheel events in UE4.27?