Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Bug Huge performance regression when upgrading to 1.18.16 from 1.16.16

Discussion in 'Addressables' started by KarimTA, Oct 14, 2021.

  1. KarimTA

    KarimTA

    Joined:
    Jan 8, 2019
    Posts:
    27
    When updating to the latest 2019.4LTS, the Addressables updated from 1.16.16 to 1.18.16.
    We immediatly suffered a 100% reproductible several minutes long freeze when loading our game.

    After investigating, this appears to be caused by the very expensive delegate binding in the AssetReference constructor:

    NfTOf7RC5c.png
    uXGTVcBBDa.png



    Here are the different constructors before and after the update:

    AssetReferenceConstructor_1.16.16.png


    AssetReferenceConstructor_1.18.16.png

    Building the game took a huge hit as well. 3h of building addressables didn't even go past the scene dependency stage (usually it takes us 20 to 30min to build the whole thing).

    Thankfully we were able to downgrade back to 1.16.16 as the new version is plainly put unusable as is.

    Is this known/fixed in later versions?
     
    PiotrK_AR, dmaj and TacticalShader like this.
  2. TreyK-47

    TreyK-47

    Unity Technologies

    Joined:
    Oct 22, 2019
    Posts:
    1,796
  3. dmaj

    dmaj

    Joined:
    Feb 5, 2019
    Posts:
    3
    I have noticed this issue as well, I'm working in a big project, with thousands of AssetReferences in managed memory. This callback operation in AssetReference constructor costs us around 15s on every Domain Reload (script change, enter playmode, etc.), so it's a huge problem for us.

    I haven't found it reported on issue tracker, so I have filed a bug report with sample project and easy reproduction, but it was 21 days ago and no response yet. I'm afraid that the case will be forgotten and won't be fixed anytime soon. Could someone look at it and push the case further?

    My case number: 1378457
     
  4. KarimTA

    KarimTA

    Joined:
    Jan 8, 2019
    Posts:
    27
    dmaj likes this.