Becomes unresponsive when creating Matinee movie

When I try to make a Matinee movie it becomes unresponsive and I have to force quit. I am on a Mac

Hi VoidGoat,

Can you give me more details on your system specs, including what OS version you’re on?

Are you getting a crash report window in addition to it becoming unresponsive?

-.

I am having this issue too on 4.11.2 I’m on Mac OS version 10.11.4 I’m on a mid 2014 Macbook Pro with 16 gigs of RAM and an NVIDIA GeForce GT 750M graphics card. There are two different behaviours when rendering a video sequence or image sequence. With an image sequence I get a system hang (beachball) and no crash report window. The crash happens immediately upon starting the export. Sometimes the first frame is displayed in the preview window but no image files are generated in the specified export folder. When saving a video sequence I get a crash report. Here’s an excerpt from it (too large to paste in this box!):

MachineId:518274665C4A2503219C31BE57961AE9
EpicAccountId:f4da20db119a4a36815b51ccc29c8a8b

SEGV_MAPERR at 0x7fbed8e00000

_platform_memmove$VARIANT$Haswell Address = 0x7fff8598bf49 (filename not found) [in libsystem_platform.dylib]
Unknown() Address = 0x13eb4e51d (filename not found) [in GeForceMTLDriver]
FMetalSurface::Lock(unsigned int, unsigned int, EResourceLockMode, unsigned int&) Address = 0x13fa4af28 (filename not found) [in UE4Editor-MetalRHI.dylib]
FMetalDynamicRHI::RHIMapStagingSurface(FRHITexture*, void*&, int&, int&) Address = 0x13fa4a724 (filename not found) [in UE4Editor-MetalRHI.dylib]
UE4Function_Private::TFunctionRefCaller const&, TFunction)::$_0, void (FRHICommandListImmediate&)>::Call(void*, FRHICommandListImmediate&) Address = 0x120c59d15 (filename not found) [in UE4Editor-MovieSceneCapture.dylib]
TGraphTask const&, TFunction)::EURCMacro_ResolveCaptureFrameTexture>::ExecuteTask(TArray&, ENamedThreads::Type) Address = 0x120c58a3c (filename not found) [in UE4Editor-MovieSceneCapture.dylib]

An update: I’ve installed 4.10.4 and the movie export function works perfectly. My problem definitely seems to be related to 4.11 specifically.

Hi OwainRich,

We were able to get a crash in 4.11, but it is a different callstack from yours. Our crash doesn’t reproduce in 4.12 though. Could you check out 4.12 Preview and let me know if it still occurs.

-.

Hi Everybody,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

-.