Announcement

Collapse
No announcement yet.

[SOLVED] Easy way to debug <Fatal-Error> editor crashes at startup (after creating new FPS Project)?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [EDITOR] [SOLVED] Easy way to debug <Fatal-Error> editor crashes at startup (after creating new FPS Project)?

    Its rare you see a 'Fatal Error' dialog at startup with no other useful info. It can happen if you run out of disk space and auto-save kicks in etc. I'm seeing another scenario where the Editor is crashing after creating a new FPS project. It doesn't happen with any other project type. The crash occurs just before the editor window should pop up (95% / 96% loading point). Anyone have ideas or know which logs to check? Its affecting airgapped PC's using 4.18 binary build (no debug-symbols installed).
    Last edited by EntrpriseCustomr; 10-10-2019, 02:56 AM.

    #2
    ..........Bump........

    Comment


      #3
      Install debug symbols and launch c++ project running in editor mode from Visual Studio, that will launch the UEditor with debugger attached and point to where it is crashing.
      | Savior | USQLite | FSM | Object Pool | Sound Occlusion | Property Transfer | Magic Nodes | MORE |

      Comment


        #4
        Narrowed the crash down... Its happening just prior to the Map-Check completing and seems to be tied to static lighting, and on some level
        compiling shaders (aborts at the same point everytime during LogTexture: Display: Building Textures).

        I generally only use Dynamic Lighting. But as the FPS template has static lighting, I disabled the BuiltAsset.uasset for the FirstPersonExampleMap - and now finally SUCCESS!!! The new FPS template project loads up in the Editor... That gave me the idea to try Building Lighting on a new TPS template project instead, AND that is crashing (even if the TPS template map itself loads up in the editor just fine).

        So what's going on... Anyone seen this before? - BTW: Testing on a second rig shows no issues with either the engine install or the project. There's no obvious 'D3D device lost errors' or anything in the logs either.... (Using an RTX-2070 rig and UE4.18).
        Last edited by EntrpriseCustomr; 10-17-2019, 07:18 AM.

        Comment


          #5
          ...........Bump..........

          Comment


            #6
            You'd have provided callstack (information from Crash Reporter, also included at the of Log file in case of crash), so anybody could help you in any way.
            You need to download debug symbols for that, as mentioned above. There's a chance someone would guess the reason for your crash.

            Can't guarantee that... Often the best would be to catch a crash in Visual Studio and inspect data. You would even get asset causing crash.
            Otherwise, maybe the best solution for you would be just removing part of assets from the crashing map, repeat it until you'd isolate which asset is crashing.

            Comment


              #7
               
              Spoiler

              Can you infer anything at all from the screengrab above dude? The crash occurs after attempting to Build Lighting on a new ThirdPerson template. BTW: The rigs are airgapped (offline machines)... So its not going to be that simple to install symbols and find a full standalone version of VS...
              Last edited by EntrpriseCustomr; 10-17-2019, 06:07 PM.

              Comment


                #8
                Solved: Missed one dependency: Nvidia-Texture-Tools - nvtt_64.dll - msvcr120.dll...

                Comment

                Working...
                X