# Device ensure: IsInGameThread(): FCoreRedirects can only be initialized on the game thread 

**URL:** <https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258>\
**Category:** Mobile\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [October 1, 2025, 4:50pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258 "2025-10-01T16:50:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 1, 2025, 4:50pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258/1 "2025-10-01T16:50:36Z")

</div>

After upgrading to 5.5.4 (from 5.4.4) we have started receiving a lot of ensures from mobile users in our crash reporting. Sadly we currently have an issue with mixed Java / Native backtraces, so we don’t have any of the C++ callstack available:

The ensure is this:

```auto
Ensure condition failed: IsInGameThread() [File:./Runtime/CoreUObject/Private/UObject/CoreRedirects.cpp] [Line: 1374]
FCoreRedirects can only be initialized on the game thread.

```

Is this a known issue in 5.5.4? Is there a fix we can backport for it? We are not seeing this in editor.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 1, 2025, 4:50pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258/2 "2025-10-01T16:50:40Z")

</div>

**Steps to Reproduce**

---

<div class="post-metadata">

**Author:** ![step\_jac\_eg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@step\_jac\_eg](https://forums.unrealengine.com/u/step_jac_eg)\
**Post date:** [October 1, 2025, 7:45pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258/3 "2025-10-01T19:45:21Z")

</div>

Hi Jorgen,

Can you share the call stack leading to this assertion?

Best regards.

---

<div class="post-metadata">

**Author:** ![step\_jac\_eg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@step\_jac\_eg](https://forums.unrealengine.com/u/step_jac_eg)\
**Post date:** [October 7, 2025, 11:54pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258/4 "2025-10-07T23:54:03Z")

</div>

Hi Jorgen,

Thanks for the additional details. This appears to be an issue that was resolved after 5.5.4 release at CL# [36713788](https://github.com/EpicGames/UnrealEngine/commit/a7fcf0cbad6d199f5e8f246add45f0c7543951d0).

Best regards.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 7, 2025, 11:08pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258/5 "2025-10-07T23:08:37Z")

</div>

Hi, I am not able to do so, because our ensure reporting is not currently reporting useful callstacks.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 7, 2025, 11:24pm UTC](https://forums.unrealengine.com/t/device-ensure-isingamethread-fcoreredirects-can-only-be-initialized-on-the-game-thread/2672258/6 "2025-10-07T23:24:42Z")

</div>

I take that back! I successfully coaxed it to produce a useful callstack on iOS, though not on Android. Here’s the call stack:

```auto
31 FCoreRedirects::Initialize (cxx_atomic_impl.h:1375)
 
32 operator& (CoreRedirects.h:65)
 
33 FCoreRedirects::AddKnownMissing (CoreRedirects.h:1720)
 
34 FLinkerLoad::AddKnownMissingPackage (LinkerLoad.cpp:6676)
 
35 FAsyncPackage::CreateLinker (AsyncLoading.cpp:6293)
 
36 FAsyncPackage::Event_CreateLinker (AsyncLoading.cpp:1836)
 
37 FAsyncPackage::GetLinkerRoot (AsyncLoading.h:422)
 
38 operator (Control.cpp:1806)
 
39 decltype (Invoke.h:47)
 
40 …::Function::TFunctionRefCaller<…> (AsyncLoading.h:315)
 
41 …::Function::TFunctionRefBase<…> (Function.h:477)
 
42 TFunction<…> (Function.h:743)
 
43 TFunction<…> (Function.h:743)
 
44 FAsyncLoadEvent::~FAsyncLoadEvent (AsyncLoadingThread.h:29)
 
45 FAsyncLoadEvent::~FAsyncLoadEvent (AsyncLoadingThread.h:29)
 
46 FAsyncLoadEventQueue::PopAndExecute (AsyncLoadingThread.h:112)
 
47 FAsyncLoadingThread::ProcessAsyncLoading (Function.h:4396)
 
48 FAsyncLoadingThread::TickAsyncThread (AsyncLoading.cpp:5300)
 
49 SharedPointerInternals::FSharedReferencer<…> (SharedPointerInternals.h:602)
 
50 SharedPointerInternals::FSharedReferencer<…> (SharedPointerInternals.h:601)
 
51 TSharedPtr<…> (SharedPointer.h:664)
 
52 TSharedPtr<…> (SharedPointer.h:664)
 
53 FFlushRequest::~FFlushRequest (AsyncLoadingThread.h:171)
 
54 FFlushRequest::~FFlushRequest (AsyncLoadingThread.h:171)
 
55 FAsyncLoadingThread::Run (SharedPointerInternals.h:5226)
 
56 FRunnableThreadPThread::Run (PThreadRunnableThread.cpp:25)
 
57 FRunnableThreadPThread::_ThreadProc (PThreadRunnableThread.h:188)
 
58 _pthread_start (libsystem_pthread.dylib)
 
59 thread_start (libsystem_pthread.dylib)

```
