Search Unity

What are persistent Temp Job allocations used for in 2019?

Discussion in 'iOS and tvOS' started by VictorChow_K, Jun 5, 2020.

  1. VictorChow_K

    VictorChow_K

    Joined:
    Jan 16, 2019
    Posts:
    9
    I'm trying to reconcile the difference in memory used after some development and an upgrade from 2018.4.14f1 to 2019.3.10f1 on iOS. For example, 2019 uses 80-100MB more memory on a specific device in the same scenario that can't be accounted for by additional content. Details were originally posted in the Profiler Preview forum, but I have some related questions.

    I discovered some entries in the 2019 Native Memory Region section with the following labels:
    • ALLOC_TEMP_JOB_ASYNC (block: <id>) [size description]
    • Stack Allocator: ALLOC_TEMP_THREAD: Memory Block
    • Stack Allocator: ALLOC_TEMP_THREAD: Virtual Memory Block
    They are not present in 2018 and total at least 35MB. 2018 has only 1MB worth of similar allocations labeled ALLOC_TEMP_JOB (block: <id>).

    What high-level feature(s) could these pertain to that I could enable/disable to further determine their origin? Can I cross-examine this with anything in an Instruments Allocation profile?