Details

    • Similar Issues:

      Description

      While uncertainty is an issue official or plug-ins.

      Use 5.0.0f4 build will stop.
      But 4.6.1 normal.

      Parameters
      -quit -batchmode -buildWindows64Player "$WORKSPACE\output\bin\FishHunter.exe" -projectPath "$WORKSPACE"

        Attachments

          Issue Links

            Activity

            Hide
            lacostej lacostej added a comment - - edited

            This is suprising because I've been using many beta builds without problem (on Mac only though).

            It might be a editor.log problem or a buildWindows64Player argument issue. Could you try adding the editor log argument to log to a file under the job worspace ?

            Show
            lacostej lacostej added a comment - - edited This is suprising because I've been using many beta builds without problem (on Mac only though). It might be a editor.log problem or a buildWindows64Player argument issue. Could you try adding the editor log argument to log to a file under the job worspace ?
            Hide
            jiowchern jiowchern chen added a comment - - edited

            After adding -nolog can show the message.
            But in the end there is some problem. consoleText.txt can not proceed.

            Show
            jiowchern jiowchern chen added a comment - - edited After adding -nolog can show the message. But in the end there is some problem. consoleText.txt can not proceed.
            Hide
            lacostej lacostej added a comment -

            I've run into a problem on one of the betas where unity was spawning some shader compilers and not terminating them at end, causing the main process to not exit properly.

            Could you double check if there are hanging unity / shader compiler processes ? If so, maybe it's a similar bug ? In my case, I fixed the issue by modifying the shaders.

            Show
            lacostej lacostej added a comment - I've run into a problem on one of the betas where unity was spawning some shader compilers and not terminating them at end, causing the main process to not exit properly. Could you double check if there are hanging unity / shader compiler processes ? If so, maybe it's a similar bug ? In my case, I fixed the issue by modifying the shaders.
            Hide
            jiowchern jiowchern chen added a comment -

            The original project have been very empty.
            Only some Plugins like Unity Test Tools, Unity Steer, Unity VS ...

            I tried using an empty project.
            https://github.com/jiowchern/EmptyUnity5.git

            Eventually will display an error message.
            consoleText_EMptyUnity5.txt

            Show
            jiowchern jiowchern chen added a comment - The original project have been very empty. Only some Plugins like Unity Test Tools, Unity Steer, Unity VS ... I tried using an empty project. https://github.com/jiowchern/EmptyUnity5.git Eventually will display an error message. consoleText_EMptyUnity5.txt
            Hide
            lacostej lacostej added a comment -

            Have you double checked if some processes are left hanging ?

            Assuming the problem is caused by the debugger-agent access to the port, I would try a few things:

            • force exiting the process at build end (maybe using EditorApplication.Exit (ExitCode))
            • try to force the debugger agent to use a different port. Not really sure why it fails. Are you by any chance running your Windows server as a VM guest under a Linux host ? That might explain ports under 1024 failing to connect.

            I would also contact Unity support. This isn't normal.

            If you are willing to, feel free to contact me on Skype (lacostej) and maybe I can help troubleshoot this further (accessing your server would help)

            Show
            lacostej lacostej added a comment - Have you double checked if some processes are left hanging ? Assuming the problem is caused by the debugger-agent access to the port, I would try a few things: force exiting the process at build end (maybe using EditorApplication.Exit (ExitCode)) try to force the debugger agent to use a different port. Not really sure why it fails. Are you by any chance running your Windows server as a VM guest under a Linux host ? That might explain ports under 1024 failing to connect. I would also contact Unity support. This isn't normal. If you are willing to, feel free to contact me on Skype (lacostej) and maybe I can help troubleshoot this further (accessing your server would help)
            Hide
            lacostej lacostej added a comment -

            Could you try using passing unity3d some options to force a different port ?

            Maybe something like

            MONO_SDB_ENV_OPTIONS=address=127.0.0.1:40904
            

            or something like that. Check the new editor.log to see if that helps you. Today you have something

                  Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y
            
            Show
            lacostej lacostej added a comment - Could you try using passing unity3d some options to force a different port ? Maybe something like MONO_SDB_ENV_OPTIONS=address=127.0.0.1:40904 or something like that. Check the new editor.log to see if that helps you. Today you have something Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y
            Hide
            lacostej lacostej added a comment -

            Not sure if that works in the version of mono bundled in Unity

            Show
            lacostej lacostej added a comment - Not sure if that works in the version of mono bundled in Unity
            Hide
            kilianvde Kilian Van den Eynde added a comment - - edited

            Any luck or fixes for this have the exact same issue it hangs on this error message:

            Unloading 2 unused Assets to reduce memory usage. Loaded Objects now: 523.
            Total: 2.699615 ms (FindLiveObjects: 0.131413 ms CreateObjectMapping: 0.026965 ms MarkObjects: 2.520755 ms DeleteObjects: 0.017749 ms)

                • Completed 'Build.Player.WindowsStandaloneSupport' in 22 seconds (21570 ms)
                  Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
                  Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
                  Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
                  Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
                  Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
                  Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll

            I added the

            MONO_SDB_ENV_OPTIONS=address=127.0.0.1:40904

            to the player options in the editor and it stopped giving me the debugger agent error but now it just hangs.

            But it spits out the .exe and data folder and all works but my third buildstep cannot run because it doesn't exit properly.

            Show
            kilianvde Kilian Van den Eynde added a comment - - edited Any luck or fixes for this have the exact same issue it hangs on this error message: Unloading 2 unused Assets to reduce memory usage. Loaded Objects now: 523. Total: 2.699615 ms (FindLiveObjects: 0.131413 ms CreateObjectMapping: 0.026965 ms MarkObjects: 2.520755 ms DeleteObjects: 0.017749 ms) Completed 'Build.Player.WindowsStandaloneSupport' in 22 seconds (21570 ms) Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll I added the MONO_SDB_ENV_OPTIONS=address=127.0.0.1:40904 to the player options in the editor and it stopped giving me the debugger agent error but now it just hangs. But it spits out the .exe and data folder and all works but my third buildstep cannot run because it doesn't exit properly.
            Hide
            lacostej lacostej added a comment -

            Kilian,

            are there any dangling unity processes ?

            Have you tried running unity through a standard CMD ?

            Feel free to contact me on skype as explained earlier.

            Show
            lacostej lacostej added a comment - Kilian, are there any dangling unity processes ? Have you tried running unity through a standard CMD ? Feel free to contact me on skype as explained earlier.
            Hide
            lacostej lacostej added a comment -

            After investigating, it sounds like a dupe of JENKINS-24265

            Show
            lacostej lacostej added a comment - After investigating, it sounds like a dupe of JENKINS-24265
            Hide
            lacostej lacostej added a comment -

            I've made it so that the hang doesn't happen anymore when the editor.log isn't found. Closing this one until we hear more about where the editor.log should be found. It sounds like a Unity bug. Not really sure how to find out where the log is actually.

            Show
            lacostej lacostej added a comment - I've made it so that the hang doesn't happen anymore when the editor.log isn't found. Closing this one until we hear more about where the editor.log should be found. It sounds like a Unity bug. Not really sure how to find out where the log is actually.

              People

              • Assignee:
                lacostej lacostej
                Reporter:
                jiowchern jiowchern chen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: