Internal mechanism of the Profiler ??

Unity Engine
1

Hello everyone

I would like to know : What is the internal mechanism of the Profiler ?
What is it doing behind the scene apart of measuring execution time (CPU) of each methods ?
Especially, what’s going on with the GPU in OpenGL or DirectX ?

I am asking this due to an unsolved bug while running in OpenGL on Windows 7. This bug, a huge lag (FPS=3) get “solved” when I connect the Profiler (occurs in Editor and Debug build), and reappears when I disconnect it…
So I would like to understand the internal mechanism to identify what is solving the bug, then hopefully find the source.

Thanks in advance for your support.
@N3ms

2

Probably easier to submit a bug report that includes the misbehaving project and a video that shows what happens.

3

Thank you for your reply Graham.

I would be more than happy to submit a bug report, but :

  • It is difficult to share the projects presenting this bug with an external entity for IP reason;
  • There are 3 projects (out of 10) presenting the bug, one of them is more than 2 Gb;
  • I could strip the protected and unnecessary parts to send it to you, but from my tests the bug is not present on other computers…

It’s very strange, in the editor (in OpenGL mode) when I play the game, the FPS go down to about 3. When I press Ctrl+7 to open the Profiler, the FPS is about 30 ; if I close the Profiler, the FPS get back to 3.
The same behavior is happening in the build and debug build. In DirectX, there is no problem, but I need OpenGL.

Seriously, I have tried everything at my knowledge : driver bug, windows bug, graphic card bug.
I have rebuilt the project by re-importing each assets separately, then replacing each missing components manually in the scene.
Perhaps the scene file is corrupted ? I do not know how to check that.
I have also tried in a new scene by just adding the same objects and scripts… same bug.

I have multiple computer with the same graphics card and driver version, this bug is sometimes present, sometimes not. That could point to the graphics card, but the same project was running fine back in February and other projects always run fine.

Other OpenGL programs run fine.

That’s why I am ending asking myself : why the Profiler can solve the problem ? What is it doing on the memory or the timing to clear the bug ?

Thanks again for your reply, I hope you or someone else could point me to the beginning of a clue…

4

Hello

I am especially interested in the GPU profiling part, because it seems that is not related to CPU.

Thanks for your help.

5

Anyone from Unity could help me ?
I would like to understand what the Profiler is doing with the GPU to temporally solve the issue.

6

Is there a way to get professional support with a contract from Unity ?
Like a special license including dedicated support…

7

Yes.

8

Thank you ! I did not know about that… I would have been subscribed since 6 months !!