Crash clicking on Content folder (Mac)

Hi guys,
im on macbook pro 15 using UE 4.11.1 and actually i cant open any level of my project because clicking on content folder it would crash. It doesnt happen if im on the default level.
This is the error:

SEGV_MAPERR at 0x3

FGenericPlatformMisc::RaiseException(unsigned int) Address = 0x109fd331b (filename not found) [in UE4Editor-Core.dylib]
FOutputDeviceMacError::Serialize(wchar_t const*, ELogVerbosity::Type, FName const&) Address = 0x10a164ee6 (filename not found) [in UE4Editor-Core.dylib]
FOutputDevice::Logf(wchar_t const*, …) Address = 0x10a2596f7 (filename not found) [in UE4Editor-Core.dylib]
FDebug::AssertFailed(char const*, char const*, int, wchar_t const*, …) Address = 0x10a2279c4 (filename not found) [in UE4Editor-Core.dylib]
___ZN17FMetalCommandList6CommitEPU27objcproto16MTLCommandBuffer11objc_objectb_block_invoke Address = 0x13fbcf2a0 (filename not found) [in UE4Editor-MetalRHI.dylib]
-[_MTLCommandBuffer didComplete:error:] Address = 0x7fff936325e8 (filename not found) [in Metal]
-[MTLIOAccelCommandBuffer didComplete:error:] Address = 0x7fff9360aee1 (filename not found) [in Metal]
-[_MTLCommandQueue commandBufferDidComplete:timestamp:error:] Address = 0x7fff93636155 (filename not found) [in Metal]
ioAccelCommandQueueBlockFenceCallback Address = 0x7fff909b91f2 (filename not found) [in IOAccelerator]
IODispatchCalloutFromCFMessage Address = 0x7fff859346a2 (filename not found) [in IOKit]
_IODispatchCalloutWithDispatch Address = 0x7fff85934721 (filename not found) [in IOKit]
dispatch_mig_server Address = 0x7fff8ab08a4b (filename not found) [in libdispatch.dylib]
_dispatch_client_callout Address = 0x7fff8aaf440b (filename not found) [in libdispatch.dylib]
_dispatch_source_latch_and_call Address = 0x7fff8ab04675 (filename not found) [in libdispatch.dylib]
_dispatch_source_invoke Address = 0x7fff8aaf8a83 (filename not found) [in libdispatch.dylib]
_dispatch_queue_drain Address = 0x7fff8aaf9200 (filename not found) [in libdispatch.dylib]
_dispatch_queue_invoke Address = 0x7fff8aaff707 (filename not found) [in libdispatch.dylib]
_dispatch_root_queue_drain Address = 0x7fff8aaf7d53 (filename not found) [in libdispatch.dylib]
_dispatch_worker_thread3 Address = 0x7fff8aaf7b00 (filename not found) [in libdispatch.dylib]
_pthread_wqthread Address = 0x7fff8693a4de (filename not found) [in libsystem_pthread.dylib]
start_wqthread Address = 0x7fff86938341 (filename not found) [in libsystem_pthread.dylib]

Hi Daryen,

I am not able to find your machine id on our Crash Reporter site? Did you hit submit on the Crash Reporter window? If not, please try this again and hit submit when prompted.

Thanks,

.

I did it now

Can you provide more information about when this crash occurs so that we can try to reproduce the issue on our end?
Also, please provide as many of the following as possible:

  1. Your Mac’s specs. You can find this in the Apple menu >About This Mac>More Info> Add the information from this window (serial # not necessary).
  2. The “System Report:” Apple menu >About This Mac > System Report>Hardware (All information listed in the “Hardware Overview.”) You can cut and paste this information or provide screen shots, whichever is more convenient.
  3. The UE4.log (Located: ~/Library/Logs/Unreal Engine/Editor/)
  4. The ProjectName.log (Located: ~/Library/Logs/Unreal Engine/ProjectNameEditor/)

Providing this information and appropriate logs will help us track down and isolate the source of the bug as quickly and efficiently as possible. *Also, I was still not able to track your crash with the above Machine ID. Please try hitting submit again next time this crash occurs.

Thanks for your cooperation,

.

Hi
Any solution to this? I have the same problem on an iMac when loading a project. Gets to Loading … 95% then crashes with similar error log to the above.

@Skirrah,

Please start a new AnswerHub post and include the information I’ve requested on this post. We are currently researching an apparent conflict between running Metal on Mac and UE 4.11. However, we need a project and/or consistent repro steps in order to isolate the cause of the crash.

Thanks,

.

Hi Daryen,

Since we have not heard back from you in a few days, we are closing this post for tracking purposes. However, if you are still experiencing a crash when clicking on the Content folder, please respond with the requested information above and we will continue to investigate. Also, be sure you have hit “submit” on the Crash Report pop up window so we can cross reference this with other data.

Thanks,

.