CRITICAL: v41.20 Causing Hard Client Crashes on All PC/Console Platforms

General Issues and Bug Reporting
, , ,
1

Summary

Since the v41.20 update, players on my map Winter Rockets VS Cars (0105-1573-8859) are experiencing random client crashes where the entire Fortnite application completely closes.

This issue is clearly reflected in the map’s recent analytics following the update:

Playtime and Session Time: Both metrics have dropped significantly.
Bounce Rates: There is a noticeable spike across all platforms, with the exception of mobile.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

  1. Play a game and wait for the server to crash

Expected Result

  1. Server should not crash

Observed Result

  1. Whole Fortnite crashes

Platform(s)

All platforms except mobile

Island Code

0105-1573-8859

Upload an image

session time.png
session time.png542×501 31 KB

3

kuva
kuva744×336 9.17 KB

This is the screen you get when the game crashes on PC

4

After investigating the game logs:

CrashGUIDs:

  • UECC-Windows-B0AFC6A444F1B92B34E30488FD2A169D
  • UECC-Windows-D0C7BF274AD58EE1A39895982F30B4D8

The issue appears to happen when the full game ends and Fortnite resets the minigame for the next game.

The client crashes during the transition from PostRoundEnd to MinigamePostGameReset. During respawn, AFortPlayerControllerAthena::HasStreamingLevelsCompletedLoadingUnLoading() reports that the Winter_Rockets_VS_Cars Level Instance is still loaded around the time UWorldPartition::Uninitialize is running.

Immediately before the crash, the logs repeatedly report that it is not safe to respawn because the Level Instance is still loaded. The client then crashes with:

EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000648

Two separate crashes produced the same exception address and the same call stack.

More precise reproduction steps:

  1. Join island 0105-1573-8859.
  2. Play until the complete game finishes.
  3. Wait for the transition from the end-of-game screen into the next full game.
  4. During the minigame reset and player respawn process, the Fortnite client may completely close.
  5. This has reportedly affected PC and console players since v41.20.

Please correlate the two CrashGUIDs with the internal crash reports and symbolicate the call-stack addresses for build CL-55550516.

1 Like
5

Sorry you are experiencing these issues and thank you for the report!

I have escalated this with the team, we’ll have someone look into this

1 Like
8

FORT-1126843’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.

9

I researched the issue with AI with multiple PCs, where some crashed and some didn’t. I tried removing multiple different props and devices but it didn’t have any effect on the crashes. AI had this as the conclusion for the crashing issue:

Two clients in the same session unloaded the same LevelInstance_15 at the same synchronized moment. The alive client with a valid pawn completed the transition. The eliminated spectator client with Pawn: None crashed 606 ms after UWorldPartition::Uninitialize with access violation 0x648.