Memory Leak in Clone Function

Now that it works quite well on the Mac (since we finally can eject a volume after cloning without leaving Resolve) I've been using the clone function quite frequently for a while. Until now the size of my cards and the files was reasonably small and all went well.
I even prefer it to Offload now, which has a bug regarding the date/time stamp.

But recently I needed to clone pretty large files from a 1 TB SSD (out of the Shogun) with single files reaching half a TB (very long 4K recordings in ProRes HQ).
Now I'm observing a memory leak that can lead to a complete stall on my Laptop (with only 16 GB RAM). When I observe the memory use it is constantly increasing while cloning is active until it leaves no more room for stable function. Needles to say that Resolve is crashing in these cases if I continue to work with it (after all, cloning works in the background).

Now that I know about this, I can see the increasing use of memory with smaller media too. The problem might be to get a proper crash log, since the function is just getting slower and slower until the "time remaining" is increasing instead of decreasing. It doesn't really crash, but I need to kill Resolve, since the stop button doesn't help,

Anybody else seeing this?