Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Bug Hard stuck burst compiler

Discussion in 'Burst' started by THALL-Flaim, Mar 7, 2023.

  1. THALL-Flaim

    THALL-Flaim

    Joined:
    Jul 19, 2022
    Posts:
    4
    been stuck for over a week on burst compiler - gets to 87% and just hangs static with the seconds counter rising - eating cpu and memory. HELP!
     

    Attached Files:

  2. DevDunk

    DevDunk

    Joined:
    Feb 13, 2020
    Posts:
    4,974
    Which unity version? Tried updating?
    Does it also happen when you paste your code in a brand new project (in the latest version)?
     
  3. Lee_Hammerton

    Lee_Hammerton

    Unity Technologies

    Joined:
    Jul 26, 2018
    Posts:
    118
    I`m sorry to hear that,

    How long have you waited (the fact memory and cpu usage is increasing, implies it is still compiling)? The screenshot doesn't show its been stuck for a week? It's possible depending on cpu specs of host machine and size/complexity of the module being compiled thats its simply taking a while. Note Burst is designed to be async, you don't have to wait for it to finish, you can continue to work in the background while its compiling, it just won't run the bursted version of code that isn't finished compiling (reverting back to the mono version of the code).

    If it is truly getting stuck, then the best course of action is to submit a bug report with a project attached that reproduces the problem.

    By the way, when reporting burst issues on the forum, a good baseline of information to begin with is the Burst Version, the Unity Version and if possible, how we might re-create the problem - e.g. a code snippet that causes the issue.
     
    tim_jones and DevDunk like this.
  4. ehww

    ehww

    Joined:
    Jan 30, 2020
    Posts:
    11
    this happens here too, currently on 1.8.4

    It never completes even when left all day. Is this related to the file lock issue that is ruining productivity?
    Is there any way to see what library it is getting stuck on? Or do I have to go through and remove [BurstCompile] one at a time?

    *Edit* Also worth noting, when Burst is stuck in this state, closing the Unity editor seems to result in being stuck on Application.Shutdown.CleanupMono so the editor never closes and has to have the process force terminated
     
    Last edited: Apr 28, 2023
  5. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    287
    Hi @ehww - sorry to hear you're having the same problem. Please could you submit a bug report with a project attached that reproduces the problem?

    There's not an easy way to see what library it's getting stuck on. For now, removing one [BurstCompile] at a time is the way to go - or submit a bug report, assuming the problem is reproducible, and we'll take a look.
     
    DevDunk likes this.
  6. tivlaser

    tivlaser

    Joined:
    Jun 23, 2015
    Posts:
    1
    Unity 2022.2.19
    After updating from burst 1.5.4 to 1.6.0(in 1.8.4 the same), the compiler is getting stuck. The reason seems to be an int[] with over 800,000 elements. Were there any changes in 1.6.0 that could be causing this? Is there a way to solve this problem?
     
  7. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    287
    @tivlaser please could you submit a bug report (via Help > Report a Bug)? There may have been a difference in the lower-level parts of Burst between 1.5.4 and 1.6.0 which made it get stuck compiling an array with over 800,000 elements, but if we could see the actual code causing the problem, that would help us diagnose it more quickly.