Bug big string allocations (GC.alloc) appearing inside setup of the URP when using 2 cameras onscreen

I am using 2022.3.7f1 with URP 14.0.8 and am noticing some really odd gc allocs going on when using two cameras on the screen at once. Here's the readout from deep profiling. It seems to be related to the use of string allocations during the setup of the scriptable renderer, and it happens for each of the cameras on every frame. It doesn't happen when I am only using a single camera on screen. I had read about similar issues in older URP releases, but they were reported as resolved by this release.

for reference, both cameras are active and enabled, but one is an "inset minimap" created by changing its output x,y,w, and h to be in the lower right corner

 

Maybe make a bug report if no staff responds

 

Will do that, just figured I'd also be open to the "you're just doing/interpretting it wrong..." solutions.

 

I personally don't see why render textures/multiple cameras would require strings to be modified unless your code calls the name or something.
But I don't work a ton with multiple cameras, so maybe someone else knows more

 

And this is happening deep inside the URP code, so I can't imagine what I'm doing that might trigger that. I was thinking if I were doing something in render textures, or something else that might wind up causing some resetting and allocation somewhere, but strings?!? I wasn't expecting to see that as the culprit.