Search Issue Tracker

Fixed in 5.4.0

Votes

0

Found in

5.4.0b1

Issue ID

759440

Regression

Yes

5.4 Culling WaitingForJob Performance Spikes (30-70ms) In The Profiler

Camera

-

To reproduce follow the steps:
1. open Unity
2. create a new scene and add a sphere in the origin (or load the testscene)
3. Run in editor with profiler open
4. Notice the spikes in profile every few seconds

Screenshot:
https://intra.unity3d.com/fogfiles2/75xxxx/759440_qf3vvqp0cgn1fgj7/case_759440-CullWaitingForJob.png

Regression from 5.3.x.
Not reproducible in 5.3.1p4

Reproduced in 5.4.0b1, 5.4.0b3

Note:
Similar bugs have been reported for 5.0.x (case 665710)
Spikes disappear when the scene is completely empty.

Additional Information:
Tester attached cpu and gpu dxdiag information as this issue might be related to certain devices or drivers.

Comments (10)

  1. ralphyua

    Aug 26, 2018 20:00

    I am also having this issue in 2017.2.0f3. It says that it was fixed. What version fixed this problem?

  2. BlandonDu

    Aug 07, 2017 08:42

    Still happening in 2017.1.f3, it takes sometimes more than 160ms for one spike!

    more specifically on these jobs: "cullscenedynamicobjects","cullobjectswithoutumbra"

  3. JuozasK

    Mar 28, 2017 07:39

    A bit late, but "Reproduced" means that it was possible to re-create the bug/issue on the versions mentioned.

  4. DrKucho

    Nov 28, 2016 17:44

    its not fixed , i have these on 5.4.1 and 5.4.2 and 5.4.3
    do we need to open another issue? or someone is reading this?

  5. phasiclabs

    Nov 24, 2016 10:01

    I tracked down stalls in our game to exactly this issue - it's happening in 5.4.1p2.

  6. romatallinn

    Oct 25, 2016 11:16

    Still have in 5.4.1f1

  7. xavier-heimgartner

    Oct 17, 2016 00:00

    I'm still getting performance spikes in WaitingForJobGroups in Unity 5.5.0b7.
    CullSceneDynamicObjects produces performance spikes up to 60ms.

  8. jdb1218

    Aug 30, 2016 20:57

    Also experiencing this on 5.4.0f3.

  9. _rmrtn

    Aug 30, 2016 14:38

    I still experience this issue in 5.4.0p3 while it is not present in 5.3.6f1. It is currently blocking us from upgrading to 5.4.0. Could you please reopen. Thanks!

  10. Assembler-Maze

    Jun 15, 2016 18:01

    What does "Reproduced in 5.4.0b1, 5.4.0b3" means? Is it fixed or not in 5.4.0?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.