Search Unity

Bug [Unity 2022.2.0f1] JobWorkerCount not working anymore. 100% cpu usage

Discussion in 'Editor & General Support' started by dyox, Dec 26, 2022.

  1. dyox

    dyox

    Joined:
    Aug 19, 2011
    Posts:
    619
    Hello, after updating our game to Unity 2022.2.0f1, we noticed that all servers were using 100% cpu (128+ cores).

    It seems that:
    Code (CSharp):
    1. Unity.Jobs.LowLevel.Unsafe.JobsUtility.JobWorkerCount = xx;
    Is not working anymore. (Tested on Awake,Start,Update,etc)

    Tested in Editor, Build and server Batchmode. (Windows 7,10, 11)

    image.png

    {
    "dependencies": {
    "com.unity.2d.sprite": "1.0.0",
    "com.unity.2d.tilemap": "1.0.0",
    "com.unity.addressables": "1.21.1",
    "com.unity.ai.navigation": "1.1.1",
    "com.unity.burst": "1.7.4",
    "com.unity.collections": "1.2.4",
    "com.unity.ext.nunit": "1.0.6",
    "com.unity.formats.fbx": "4.2.0",
    "com.unity.ide.rider": "3.0.16",
    "com.unity.ide.visualstudio": "2.0.16",
    "com.unity.ide.vscode": "1.2.5",
    "com.unity.memoryprofiler": "1.0.0",
    "com.unity.postprocessing": "3.2.2",
    "com.unity.probuilder": "5.0.4",
    "com.unity.settings-manager": "2.0.1",
    "com.unity.shadergraph": "14.0.4",
    "com.unity.test-framework": "1.1.33",
    "com.unity.textmeshpro": "3.0.6",
    "com.unity.timeline": "1.7.2",
    "com.unity.ugui": "1.0.0",
    "com.unity.xr.legacyinputhelpers": "2.1.10",
    "com.unity.modules.ai": "1.0.0",
    "com.unity.modules.androidjni": "1.0.0",
    "com.unity.modules.animation": "1.0.0",
    "com.unity.modules.assetbundle": "1.0.0",
    "com.unity.modules.audio": "1.0.0",
    "com.unity.modules.cloth": "1.0.0",
    "com.unity.modules.director": "1.0.0",
    "com.unity.modules.imageconversion": "1.0.0",
    "com.unity.modules.imgui": "1.0.0",
    "com.unity.modules.jsonserialize": "1.0.0",
    "com.unity.modules.particlesystem": "1.0.0",
    "com.unity.modules.physics": "1.0.0",
    "com.unity.modules.physics2d": "1.0.0",
    "com.unity.modules.screencapture": "1.0.0",
    "com.unity.modules.terrain": "1.0.0",
    "com.unity.modules.terrainphysics": "1.0.0",
    "com.unity.modules.tilemap": "1.0.0",
    "com.unity.modules.ui": "1.0.0",
    "com.unity.modules.uielements": "1.0.0",
    "com.unity.modules.umbra": "1.0.0",
    "com.unity.modules.unityanalytics": "1.0.0",
    "com.unity.modules.unitywebrequest": "1.0.0",
    "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    "com.unity.modules.unitywebrequestaudio": "1.0.0",
    "com.unity.modules.unitywebrequesttexture": "1.0.0",
    "com.unity.modules.unitywebrequestwww": "1.0.0",
    "com.unity.modules.vehicles": "1.0.0",
    "com.unity.modules.video": "1.0.0",
    "com.unity.modules.vr": "1.0.0",
    "com.unity.modules.wind": "1.0.0",
    "com.unity.modules.xr": "1.0.0"
    }
    }
     
    Last edited: Dec 26, 2022
  2. dyox

    dyox

    Joined:
    Aug 19, 2011
    Posts:
    619
    Bump
     
  3. dyox

    dyox

    Joined:
    Aug 19, 2011
    Posts:
    619
    Bump
     
  4. dyox

    dyox

    Joined:
    Aug 19, 2011
    Posts:
    619
    We had to roll back to version 2022.1.24f.
     
    Last edited: Feb 6, 2023
    W3DG likes this.
  5. kevinmv

    kevinmv

    Unity Technologies

    Joined:
    Nov 15, 2018
    Posts:
    51
    Thanks, this was indeed a regression but should be fixed and available in 2022.2.71.

    All the best,
    Kev