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. The 2023.1 beta is now available for testing. To find out what's new, have a look at our 2023.1 feature highlights.
    Dismiss Notice

2017.3b2 UGUI Canvas Memory Leak

Discussion in '2017.3 Beta' started by Player7, Oct 7, 2017.

  1. Player7

    Player7

    Joined:
    Oct 21, 2015
    Posts:
    1,533
    Following on from the previous in 2017.2 bug ( https://forum.unity.com/threads/2017-2-case-939424-shared-ui-mesh-memory-leak.486912/ )

    ..this problem is still here for me both in 2017.2 and 2017.3....

    I've included a project with it, case number: 957245



    Minute or so later...


    MemoryProfiler itself was also adding to the used memory at one point it had used 9gb+ altogether, that issue might be separate problem with 2017.3 and the memory profiler though.
     
    Prodigga, Peter77 and MrEsquire like this.
  2. Player7

    Player7

    Joined:
    Oct 21, 2015
    Posts:
    1,533
    Well this issue has been around for what a few months now.. 2017.3.b7 (not that this build is usable as prefab saving is broken) and I still can't use the profiler without it chewing through memory thanks to ugui canvases...
     
    Prodigga likes this.
  3. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,045
    Hi Player7,
    We have a fix for this issue in our repositories. It's going through review and will hopefully be in one of the upcoming beta releases (not before b11).
     
  4. Player7

    Player7

    Joined:
    Oct 21, 2015
    Posts:
    1,533
    I hope the prefab issues gets fixed aswel.. 2017.3 beta testing has been a write off as far doing anything productive while using it.
     
  5. Player7

    Player7

    Joined:
    Oct 21, 2015
    Posts:
    1,533
    Finally its fixed in b11

    Though the other problem with the memoryprofiler taking +30s for a snapshot is still a problem with the newer 2017.3 release, was much faster in previous unity releases.

    -edit was using old memory profiler sourcecode in the project that was taking 30s :)
     
    Last edited: Nov 29, 2017
    Peter77 likes this.