Repeated crashes when I try to edit 'Blazing Vengeance' game

Describe the bug:

Within a few seconds of me entering edit mode on Blazing Vengeance (in advanced mode) it seems to crash Unreal Engine. I have submitted several bug reports this morning. I sometimes get as far as being able to preview but often just open in editor and it crashes.

How do you cause this bug?

  • Open Crayta using Epic Games on PC
  • Click Create
  • Click Blazing Vengeance Game
  • Click Edit

Screenshots / video of bug:
I have submitted bug reports

Which platform: PC / Stadia
PC - Epic Games

Which input: Controller / keyboard + mouse
Keyboard / Mouse but I sometimes have a Stadia controller plugged into my PC.

Your Crayta username:
I0REKBYRNIS0N (note zeros instead of Os)

Game seen in (including “Hub” or “Editor for XYZ”):
Blazing Vengeance

How regularly do you see this? (E.g. 2/3 times - please try 3 times if possible):
3+ times

Time + date seen: today multiple times between 11:57 and 12:57 GMT

Version number (found in Help tab in Settings): 0.i1.86.138001

(PC only) hardware specs (upload dxdiag file if possible - Open and run DxDiag.exe - Microsoft Support):


System Information

  Time of this report: 12/15/2022, 13:03:00
         Machine name: xxx
           Machine Id: xxx
     Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
             Language: English (Regional Setting: English)
  System Manufacturer: ASUSTeK COMPUTER INC.
         System Model: ASUS TUF Dash F15 FX516PR
                 BIOS: FX516PR.328 (type: UEFI)
            Processor: 11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz (8 CPUs), ~3.3GHz
               Memory: 16384MB RAM
  Available OS Memory: 16076MB RAM
            Page File: 20178MB used, 12280MB available
          Windows Dir: C:\Windows
      DirectX Version: DirectX 12
  DX Setup Parameters: Not found
     User DPI Setting: 120 DPI (125 percent)
   System DPI Setting: 120 DPI (125 percent)
      DWM DPI Scaling: UnKnown
             Miracast: Available, with HDCP

Microsoft Graphics Hybrid: Supported
DirectX Database Version: 1.4.3
DxDiag Version: 10.00.19041.2075 64bit Unicode

Move info from crash report:

[2022.12.15-13.17.07:426][ 45]LogD3D12RHI: Warning: Force flushing command list to GPU because too many commands have been enqueued already (10003 commands)
[2022.12.15-13.17.07:542][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:543][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:543][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:544][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:545][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:545][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:545][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:546][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:546][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:546][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:547][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:547][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:548][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:548][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:549][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:549][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:549][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:550][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:550][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:550][ 46]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:556][ 46]LogEditorUI: Display: ACTUALPushFocus

[2022.12.15-13.17.07:556][ 46]LogEditorUI: Display: PushFocus: 1

[2022.12.15-13.17.07:556][ 46]LogPlayer: Showing window EEditorWindow::ActorTrees
[2022.12.15-13.17.07:556][ 46]LogPlayer: Showing window EEditorWindow::Properties
[2022.12.15-13.17.07:582][ 46]LogEditorUI: Display: PushFocus: 2

[2022.12.15-13.17.07:582][ 46]LogPlayer: Showing window EEditorWindow::AssetLibrary
[2022.12.15-13.17.07:582][ 46]LogEditorUI: Display: PushFocus: 3

[2022.12.15-13.17.07:586][ 46]LogPlayer: Showing window EEditorWindow::WorldSettings
[2022.12.15-13.17.07:627][ 46]LogEditorUI: Display: PushFocus: 4

[2022.12.15-13.17.07:652][ 46]LogEditorUI: Display: PushFocus: 5

[2022.12.15-13.17.07:668][ 47]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:673][ 47]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:673][ 47]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:674][ 47]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:675][ 47]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.07:675][ 47]LogCRDT: Display: Subscribed to collaborative session as site 1
[2022.12.15-13.17.08:366][ 55]LogRenderer: Reallocating scene render targets to support 1536x1080 Format 10 NumSamples 1 (Frame:336).
[2022.12.15-13.17.10:620][152]LogHTTP: Display: Sending 20 batched events, 6296 bytes
[2022.12.15-13.17.21:916][652]LogD3D12RHI: Error: pResource->Map(Subresource, pReadRange, reinterpret_cast<void**>(&pData)) failed
at D:\open\jen\0\release\UE4\Engine\Source\Runtime\D3D12RHI\Private\D3D12RHIPrivate.h:1181
with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_RESET

[2022.12.15-13.17.21:917][652]LogD3D12RHI: Error: [GPUBreadCrumb] Last tracked GPU operations:
[2022.12.15-13.17.21:917][652]LogD3D12RHI: Error: No Valid GPU Breadcrumb data found. Use -gpucrashdebugging to collect GPU progress when debugging GPU crashes.
[2022.12.15-13.17.21:917][652]LogD3D12RHI: Error: DRED: No PageFault data.
[2022.12.15-13.17.21:921][652]LogD3D12RHI: Error: GPU Crashed or D3D Device Removed.

Use -d3ddebug to enable the D3D debug device.
Use -gpucrashdebugging to track current GPU state.
[2022.12.15-13.17.21:933][653]LogWindows: Error: Error reentered: Fatal error: [File:D:/open/jen/0/release/UE4/Engine/Source/Runtime/D3D12RHI/Private/D3D12Util.cpp] [Line: 684]
pResource->Map(Subresource, pReadRange, reinterpret_cast<void**>(&pData)) failed
at D:\open\jen\0\release\UE4\Engine\Source\Runtime\D3D12RHI\Private\D3D12RHIPrivate.h:1181
with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_RESET

Different error this time…

image

I seem to be able to get around it if I jump straight away from the ‘Hub’ world to the ‘Main’ world. I think the hub has so many assets it is making Unreal Engine + my PC unhappy.

I’ve captured what happens in the Task Manager when this occurs. You can see that there appears to be a memory leak because the memory usage keeps increasing until Unreal Engine complains the video card has no more memory. I don’t have this issue if I load with Facebook Gaming or if I switch to the ‘Main’ world with Facebook Gaming and then open the game from Epic Games (avoiding the lobby / hub).

Wow oh wow!~

Hey there @iorek_byrnison, I have gone ahead and entered this ticket into our system.
I was unable to repro this issue, but I am sure we can get someone to further investigate this issue for us.

Thank you very much for providing all this information, this should help us out!

1 Like

Thank you. I agree that it seems specific to my setup but I have made sure drivers are up to date etc. This issue didn’t happen before the latest Crayta update so I suspect something changed. The Lobby / Hub for Blazing Vengeance has a lot of assets so I’m guessing it is pushing up against the limits. However, as the vid shows, something odd is happening where the memory usage is getting out of control.

This seemed to be resolved when some of the Christmas were removed. Must have been related to that somehow.

1 Like