TickRealtimeProbes() causes GC allocs every frame even with no reflections in game

I hope this is the right place to post this, since there is no performance forum, and according to the docs this is coming from an experimental graphics feature so...



Well, this pic says it all. In 2018.3.0f2 I am getting 17B of GC allocations every frame in a build (and editor) where there are no reflection probes, no GI is turned on, even "real time reflection probes" in quality settings is turned off. I can't seem to eliminate these calls. Tested in a new empty project.

I'm surprised that it seems no one has noticed it yet, since I can't find anything about it online.

Edit: I've submitted a bug report, the case number is 1111507

 

I would submit a bug-report and include a project to reproduce the issue, as described in this document:
https://unity3d.com/unity/qa/bug-reporting

Submitting a bug-report allows Unity Technologies to take a look at this issue.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. You can post this Case number here (in this forum thread) for Unity staff to pick up, in case they see your post.

 

Thanks! I did just that, my case number is 1111507

 

Thanks for this thread and the bug report - it is a relief to see I am not the only one.

 

@Nothke Did you get any response on your report?
Thanks in advance for any news you can share

-Pieter

 

@PieterAlbers Unfortunately no, it's still marked as open

 

That's too bad - thanks for the heads up though!

 

@PieterAlbers update! I got a reply that my report is a duplicate of this one: https://issuetracker.unity3d.com/is...reflection-allocates-17-bytes-of-gc-per-frame

So good news it's being looked at

 

Ah - that is good news for now!

Thanks for the heads up! Much appreciated!

 

I'm experiencing this as well. Good to know it's being looked at.

 

Same here. So, it's a new bug I see

 

This should be top priority. We are working hard to make sure we have no garbage per frame.

How is this NOT a regression?

@richardkettlewell if you wanna prove that regression bugs in the built-in renderer are never acceptable this is one bug that should really be looked at.

 

Same issue, using 2018.3.0f2. Even though the 17B GC is not a huge problem, I am hoping that it gets fixed soon.

 

2018.2.4f1 was just released, still no fix.

I mean, we spent so much time trying to avoid any garbage generation, and Unity just goes and generates some every frame for us, for a feature we are not using.

Surely 3 months are enough to fix this issue.

 

I have the same problem with GC.
And with .NET 4.x it's becoming even worse as StringBuilder is now generating more GC...

 

I was really hoping this would be fixed in the .4 update - I can't have Unity running around creating garbage like this. I am already creating enough by myself

 

Any news? Same problem here.

 

This is marked as "Fixed in Unity 2019.2", but on my tests I still get the 17B every frame.
There is no link to the mentioned version, and when I search for it, the only available version seems to be 2019.0.a4.
Maybe I've missed some settings? But with everything disabled that even only looks close to the related reflection stuff and in an empty default scene the 17B are there, every frame.

 

It could mean in an upcoming release.

 

Could require an HDRP update too.

 

How? Why?

It happens without having HDRP installed.

 

Surely they will include it in 2018.4 as part of LTS as releasing the update on 2019 and not 2018.3 is forcing us to upgrade to 2019.

 

Now it's marked as "Fixed 2019.1.0b5", seems like they are on the backporting way. I hope it goes down to 2018.3 soon.

 

The day has finally come! Now it's marked as fixed in 2018.3.8f1

cc @PieterAlbers

 

Tested 2018.3.8f1 and got a little shock, since I got 0.6KB every frame. But this is only because of the known mouse events stuff. Just add a GUI Layer component to the camera (yes it's deprecated) and you can marvel at 0kb

 

Tested on 2018.3.9f1 and it appears to be fixed!

 

Since here have been some people interested in having no gc allocs, this may be interesting too:

https://issuetracker.unity3d.com/is...ecuting-nativeinputsystem-dot-shouldrunupdate

This produces a total of 51B every frame, because it is called in several places

 

Ugh...

 

You say it. Currently I have a little zoo of 9 different unity versions. And 3 of them are needed to work, because of the dependencies of some assets. For a longer time I've been happy even with an alpha version, because it didn't produce garbage in an empty scene and I've accepted to export parts of the project forth and back between the other versions to get the things done. This is exasperating.

 

I'm getting this on Unity 2019.3.15f1 (HDRP): I don't have any reflection probes, has this been re-introduced, or is just a cost of using the HDRP.

 

Were you able to figure this out?
I am having the same problem on 2019.4.1f1 HDRP

 

No.

 

I opened a bug report couple of days ago.

 

Any update on that ticket? This forum goes silent but I'm seeing this issue still in 2019.4 (SRP)

 

I am thought they fixed it, I remember seeing something, but I gave up on HDRP for now and started using URP.