When i click Launch Unreal Engine 4.8.1 from Epic Games Launcher, UE4 splash screen will come up and after 80% of initialization; UE4editor will crash.
First few line of report:
Application version 4.8.1-0
... built from changelist 2591939
OS version 10.10.4.20038
Running 1 x64 processors
Exception was " SEGV_NOOP at 0x0"
Source context from ""
<SOURCE START>
<SOURCE END>
<CALLSTACK START>
objc_release Address = 0x7fff8e6a644f (filename not found) [in libobjc.A.dylib]
(anonymous namespace)::AutoreleasePoolPage::pop(void*) Address = 0x7fff8e6a4e8f (filename not found) [in libobjc.A.dylib]
_CFAutoreleasePoolPop Address = 0x7fff8f2b06f2 (filename not found) [in CoreFoundation]
Unknown() Address = 0x7fff86b07013 (filename not found) [in Foundation]
FMacPlatformProcess::CreateProc(wchar_t const*, wchar_t const*, bool, bool, bool, unsigned int*, int, wchar_t const*, void*) Address = 0x10d11ed0f (filename not found) [in UE4Editor-Core.dylib]
FDesktopPlatformMac::OpenLauncher(bool, FString) Address = 0x11635cdee (filename not found) [in UE4Editor-DesktopPlatform.dylib]
UEditorEngine::InitEditor(IEngineLoop*) Address = 0x114126c52 (filename not found) [in UE4Editor-UnrealEd.dylib]
UEditorEngine::Init(IEngineLoop*) Address = 0x11412bcd4 (filename not found) [in UE4Editor-UnrealEd.dylib]
UUnrealEdEngine::Init(IEngineLoop*) Address = 0x1147e1b8a (filename not found) [in UE4Editor-UnrealEd.dylib]
FEngineLoop::Init() Address = 0x10ced51ff (filename not found) [in UE4Editor]
EditorInit(IEngineLoop&) Address = 0x1147de877 (filename not found) [in UE4Editor-UnrealEd.dylib]
GuardedMain(wchar_t const*) Address = 0x10cee093c (filename not found) [in UE4Editor]
-[UE4AppDelegate runGameThread:] Address = 0x10cef0583 (filename not found) [in UE4Editor]
-[FCocoaGameThread main] Address = 0x10d0793ce (filename not found) [in UE4Editor-Core.dylib]
Unknown() Address = 0x7fff86b29dc2 (filename not found) [in Foundation]
_pthread_body Address = 0x7fff89e55268 (filename not found) [in libsystem_pthread.dylib]
_pthread_body Address = 0x7fff89e551e5 (filename not found) [in libsystem_pthread.dylib]
thread_start Address = 0x7fff89e5341d (filename not found) [in libsystem_pthread.dylib]
<CALLSTACK END>
Sorry to hear you’re having problems with the editor on your Mac. I’ve taken your detailed submission and filed the following report: JIRA [UE-18263]. When there is updated information on this bug, it will posted on this thread.
I don’t know what’s wrong, but perhaps if I explain what the editor is doing at this point, we may narrow this down somehow?
Where is your Epic Games Launcher installed? /Applications? Looking at the code, I find it weird that the editor would try to run a new Launcher instance if you’re launching from the Launcher app…
Normally, when you launch the editor from the launcher, the launcher gets hidden and later the editor checks if the launcher is already running. If it is, and it’s hidden, the editor does nothing else.
If it thinks the launcher is not running, it tries to find it, first in /Applications, then by looking for “Epic Games Launcher” app, then looking for “Unreal Engine” app on your disk.
Perhaps there’s something unusual about your installation that we don’t handle well?
Hi Michael, thank you for your reply. I’ve installed unreal engine via Epic Games Launcher (which is located in /Application directory). the unreal engine editor worked perfectly fine. i didn’t launch unreal engine for couple of days, and after that, when i tried to launch it, this error came up!
Is there any relation between this error and Oculus Rift runtime ? or Leapmotion ?
There shouldn’t be, unless they somehow cause stack corruption in the editor. Could you try renaming the Launcher app to something else so that the editor cannot detect it and running the UE4Editor.app directly from /Shared/UnrealEngine/4.8/Engine/Binaries/Mac/ ?
I did remove Epic Game Launcher from /Application folder and Launcher directory in /Users/Shared/UnrealEngine and did reinstall the Epic Game Launcher and now it’s working. thank you for your assistance.
Hmm. OK, I’m very glad the problem is solved, although a bit worried we didn’t really figure out what the cause was. Oh well. Let me know should you run into any other issues, or have any feedback regarding the Mac version. Thanks!