[URGENT] Project Crashing when too big

General Issues and Bug Reporting
, , , , , ,
1

Summary

I cannot really give you away to reproduce the bug, since this only got introduced in Version v32.00 or v33.00 and since then I can no longer launch a session.
I can still open the project in uefn and fly around and edit things, but as soon as click “Launch Session” it sucesfully validates and then says “Initializing” but is stuck forever at 0% and after around 30 minutes it crashes with a en error for an illegal call to StaticFindObjectFast()

[2024.12.10-17.54.02:752][518]LogGarbage: Collecting garbage
[2024.12.10-17.54.02:756][518]LogWindows: Error: appError called: Fatal error: [File:D:\build++Fortnite\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp] [Line: 445]
Illegal call to StaticFindObjectFast() while garbage collecting!

I cannot update my map and I am in desire need of help, since without updating my map, the bugs will cause all the players to leave one after another.
The Unreal Editor also stops responding in the Task Manager as if it was stuck or looping infinitely.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Project Size

Steps to Reproduce

Sadly really hard to reproduce. My Project Size is 120MB and the total Memory inside Fortnite ~98.000/100.000.

Expected Result

Session should launch normally.

Observed Result

Unreal Editor for Fortnite crashes after 30 minute wait while initializing.

Platform(s)

Windows, Unreal Editor For Fortnite

Tried on two different PCs

Island Code

0267-8380-5877

2

image
image760×602 33.9 KB

Here an image of the crash reporter

3

I think garbage collecting is a Verse related issue

1 Like
4

Do you think theres anything I can do about it?
and thank you for your reply

5

I don’t know much about verse, hopefully someone else knows

An illegal call to StaticFindObjectFast()
could be some code references a module that hasn’t been listed up top of the code in the using { } bit
maybe an asset has been deleted
maybe an asset is spatially loaded

I’m not sure what will happen if you move the verse codes out of your project folders or edit the verse files before you try to load UEFN

Do you check-in changes often to save snapshots with URC ?, maybe you could move your entire Project folder out of Fortnite Projects and sync to either your last snapshot or an earlier one.

6

hi @enething1 , @Hardcawcanary ,

Just checked the UEFN 5.6 source code at the failing location and this is the message

// Updates the suffix to be given to the next newly-created unnamed object.

Basically you have an asset/object that is not named/saved correctly.

The possible actions and run Validation Run Validation fixer check that the new asset conforms to the power of 2.

Validation and Fix-Up Tool | Unreal Editor for Fortnite Documentation | Epic Developer Community

Perhaps go back using UEFN revision control and undo the last changes

1 Like