a.konik
June 11, 2015, 1:07pm
1
Need help, help with the solution. My game crashes on startup and I see the following message:
Assertion failed: !Result || Result->LinkerLoad == Linker [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.8\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp] [Line: 1054]
KERNELBASE.dll {0x00007ff9c9fa8b9c} + 0 bytes
MyGame.exe!FOutputDeviceWindowsError::Serialize() {0x00007ff7829b3757} + 0 bytes
MyGame.exe!FOutputDevice::Logf__VA() {0x00007ff782a2db08} + 0 bytes
MyGame.exe!FDebug::AssertFailed() {0x00007ff7829f5748} + 0 bytes
MyGame.exe!LoadPackageInternal() {0x00007ff782d09470} + 0 bytes
MyGame.exe!ResolveName() {0x00007ff782d188a2} + 0 bytes
MyGame.exe!StaticLoadObjectInternal() {0x00007ff782d20fc8} + 0 bytes
MyGame.exe!StaticLoadObject() {0x00007ff782d205dd} + 0 bytes
MyGame.exe!UGameEngine::Init() {0x00007ff783686058} + 0 bytes
MyGame.exe!FEngineLoop::Init() {0x00007ff782954af5} + 0 bytes
MyGame.exe!GuardedMain() {0x00007ff7829540b8} + 0 bytes
MyGame.exe!GuardedMainWrapper() {0x00007ff7829543ea} + 0 bytes
MyGame.exe!WinMain() {0x00007ff782965fe9} + 0 bytes
MyGame.exe!__tmainCRTStartup() {0x00007ff785980a35} + 21 bytes [f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618]
KERNEL32.DLL {0x00007ff9cc0113d2} + 0 bytes
ntdll.dll {0x00007ff9ccd35444} + 0 bytes
ntdll.dll {0x00007ff9ccd35444} + 0 bytes
Crash in runnable thread SlateLoadingThread
TJ_V
June 11, 2015, 2:33pm
2
Hi a.konik,
I’m assuming your project was converted from 4.7 to 4.8, is that correct? Everything was working properly in 4.7?
Also post the entire crash reporter Callstack (make sure to submit it) and the Log & DMP files .
Hey, shouldn’t the line:
check(!Result || Result->LinkerLoad == Linker);
be:
check(Result && Result->LinkerLoad == Linker); in UObjectGlobals.cpp?
Its throwing an assert on a valid pointer with how it is currently correct?
a.konik
June 11, 2015, 7:55pm
4
after switching from 4.7 to 4.8, I had not much changed ++ code to the network portion. From the editor the game starts and everything works as before, but if you run the build, I get this message
I have the same problem but only on Android… On Windows and PIE is working good…
[2015.06.12-02.38.42:963][ 0]Log file open, 06/12/15 04:38:42
KERNELBASE.dll {0x00007ffc897f8b9c} + 0 bytes
ChasingRobbers.exe {0x00007ff6a460e907} + 0 bytes
ChasingRobbers.exe {0x00007ff6a442f858} + 0 bytes
ChasingRobbers.exe {0x00007ff6a4407fb8} + 0 bytes
ChasingRobbers.exe {0x00007ff6a47e5650} + 0 bytes
ChasingRobbers.exe {0x00007ff6a47f21c2} + 0 bytes
ChasingRobbers.exe {0x00007ff6a47fa7c8} + 0 bytes
ChasingRobbers.exe {0x00007ff6a47f9ddd} + 0 bytes
ChasingRobbers.exe {0x00007ff6a41d362a} + 0 bytes
ChasingRobbers.exe {0x00007ff6a41e6c53} + 0 bytes
ChasingRobbers.exe {0x00007ff6a467125f} + 0 bytes
ChasingRobbers.exe {0x00007ff6a47fc7b3} + 0 bytes
ChasingRobbers.exe {0x00007ff6a47ea044} + 0 bytes
ChasingRobbers.exe {0x00007ff6a41bf052} + 0 bytes
ChasingRobbers.exe {0x00007ff6a41b54ea} + 0 bytes
ChasingRobbers.exe {0x00007ff6a41b5b6a} + 0 bytes
ChasingRobbers.exe {0x00007ff6a41c8069} + 0 bytes
ChasingRobbers.exe {0x00007ff6a76f8009} + 0 bytes
KERNEL32.DLL {0x00007ffc8a6c13d2} + 0 bytes
ntdll.dll {0x00007ffc8c5e5444} + 0 bytes
ntdll.dll {0x00007ffc8c5e5444} + 0 bytes
[2015.06.12-02.42.06:428][ 0]LogExit: Executing StaticShutdownAfterError
[2015.06.12-02.42.06:430][ 0]LogWindows: FPlatformMisc::RequestExit(1)
[2015.06.12-02.42.06:430][ 0]Log file closed, 06/12/15 04:42:06
a.konik
June 12, 2015, 9:30am
7
the latest log and dumplog
xulture
June 12, 2015, 1:08pm
8
It appears that commenting that line fixes it for me. There are cases when Result is null, and when LinkerLoad is equal and not equal to Linker. Without gaining deeper understanding of the causes, curiously, cooked game runs just fine, without the check…
Farther down it has if (Result && Linker->Loader) { ResetLoaders(Result); }
That means the Check() is valid, I was wrong. If the pointer is not Valid then it continues because the IFs don’t do anything, however if the pointer is valid and not the same linker then it throws the Assert.
The problem is that it is getting a Linker that doesn’t match what it expects, I wouldn’t comment the line out, it is doing what it is supposed to be doing.
xulture
June 13, 2015, 12:57am
10
I agree – that line is good
TJ_V
June 15, 2015, 6:57pm
11
Could you also post your Crash Callstack? Just make sure to submit it as well.
a.konik
June 16, 2015, 7:53am
12
Where i can find Crash Callstack ?
TJ_V
June 16, 2015, 12:54pm
13
When the engine crashes you are generally prompted with the Crash Reporter that displays the Callstack. However, we have been tracking several reports of this error and it seems that the Crash Reporter isn’t popping up after the crash.
We are currently investigating this issue and will post back here with updates as we have them.
TJ_V
June 16, 2015, 5:18pm
14
Hi a.konik,
This has now been fixed internally. We are hoping to include it in the 4.8.1 hotfix but if you need it sooner (and are using Source) you can get the Github commit here .
Cheers,
TJ
Project created using 4.8 works just fine, but in order to work around problem in my project, removing the check() appears to avoid the problem, and, as you said, further checks in the code accommodate for cases that commented out check() doesn’t pickup.