Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. On February 28th the Feedback website will shut down and be redirected to the Unity forums. See the full post for more information.
    Dismiss Notice
  5. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  6. Unity 2018.3 is now released.
    Dismiss Notice
  7. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Building in headless mode with -quite does not shutdown unity after build

Discussion in 'Linux Editor' started by Krstn, Sep 17, 2018.

  1. Krstn


    Dec 30, 2012
    I have this command line to build my app:

    Code (CSharp):
    1. /opt/Unity-2018.2.7f1/Editor/Unity -quit -batchmode -nographics -logFile /root/stdout.log  -buildTarget WebGL -projectPath /root/projects/dw_bo_unity_positioning -executeMethod WebGLBuilder.buildDev
    My WebGLBuilder.buildDev method looks like:

    Code (CSharp):
    1.         string[] scenes = {"Assets/Scenes/Scene.unity"};
    3.         string pathToDeploy = "webglbuild-dev/unity";
    5.         PlayerSettings.WebGL.compressionFormat = WebGLCompressionFormat.Gzip;
    6.         PlayerSettings.WebGL.linkerTarget = WebGLLinkerTarget.Asm;
    7.         PlayerSettings.WebGL.memorySize = 256;
    8.         PlayerSettings.WebGL.dataCaching = true;
    9.         PlayerSettings.WebGL.exceptionSupport = WebGLExceptionSupport.FullWithStacktrace;
    10.         PlayerSettings.WebGL.useEmbeddedResources = true;
    11.         PlayerSettings.WebGL.emscriptenArgs = "-s ALLOW_MEMORY_GROWTH=1";
    13.         BuildPipeline.BuildPlayer(scenes, pathToDeploy, BuildTarget.WebGL, BuildOptions.None);
    And as stated in the title, in most of the cases, the build finishes and is "hanging", while after I kill Unity and some nodejs Unity related process the next build will pass ok.

    If someone could shed some light, I would be grateful. This is happening with versions 2018.2.2 -> 2018.2.7

    When the Unity does not shut down, in logs, I DON"T have this line:

    [Package Manager] Server::Kill -- Server was shutdown
    Last edited: Sep 17, 2018
  2. george_vasilchenko


    Sep 20, 2014
    Got the same here while building Android project. Version 2018.2.10
    Refresh: detecting if any assets need to be imported or removed ...
    Refresh: elapses 0.054368 seconds (Nothing changed)
    Refresh completed in 0.054442 seconds.
    [Package Manager] Server::Kill -- Server was shutdown
    Cleanup mono
    Checking for leaked weakptr:
    Found no leaked weakptrs.