This is a slightly common Mac crash that has occurred since 4.17.1. Users have not provided any descriptions of their actions when the crash occurred. Callstack from Log[2017.09.28-15.29.17:473][3 ...
The end of the level visibility section places a DeterminismFence. This causes the issue. The fence clips the frame range and produces a discontinuous frame ranges, e.g. 23201~24000, then 24001~24 ...
Unloading level during PIE seems to lead to an editor crash. Most easily reproducible by enabling malloc stomp. ...
Currently, using the string "None" as a hierarchical node identifier inside a Gameplay Tag (for example "A.B.C.None.D.E.F") is not disallowed by the engine, but results in some incorrect behaviors. ...
If a user creates a struct blueprint then references it in another blueprint and then deletes the struct while the editor is closed, the referencing blueprint will crash when opened. ...
When adding a niagara system that reproduces a skeletal mesh and a skeletal mesh as components to a blueprint, the niagara system immediately updates its skeletal mesh to the most recently updated s ...
This is a somewhat common Mac crash that has occurred since at least 4.14 and into 4.17. Users have not provided any descriptions of their actions when the crash occurred. The callstack contains l ...
This JIRA is being entered as a result of it being one of the top crashes in 4.13.0. Error message: Access violation - code c0000005 (first/second chance not available) Source Context: 2004 ...
This is a common crash affecting users in 4.16. User DescriptionsPressing the button to restart the basic mesh in the destruction editor causes the crash.Refreshing a Destructible Mesh that has had ...
This was originally found with Android Launch On but also occurs Launching on to Windows with a new project. This will not reproduce when using a build from PerforceogPlayLevel: Setting up ProjectP ...