Editor Freezing When Launch Fails After Having Log Window Open

Hey Guys,

Got a new issue with 4.5. What is happening is while working on an issue with Jonathan Dorman (Automation Tool Failed During Launch - World Creation - Unreal Engine Forums) with the AutomationTool failing to do a “Launch”, when having the output window open, it fails within 15 seconds to a minute later and the application hits a Not Responding state. I am actually trying to copy some log text and can’t do it quick enough to post back to Jon so it’s very consistent and it’s been probably 7 times in a row testing it so far. I checked Task Manager and there doesn’t appear to be a memory leak as the app sits at a solid 300Mb but my CPU is still ticking with UE4 taking roughly 15% CPU on a i7-4790K. Hope this helps and let me know what you need from me to test this out on my end if you have issue reproducing it on yours. Thanks!

UPDATE: This issue isn’t directly related to the Launch option but is simply when you try to select any text for that matter from the Output Log.

I am in the process of building a debug version of the editor. As a heads up, this comes from the source release of 4.5. What I am going to do is hit the Pause button in Visual Studio once I can get this up and it hits it’s Not Responding state. I have the feeling since during the freezing, it’s still asking for cycles from the CPU that maybe it’s caught in an infinite loop somewhere. I’ll take a look and try to find out more info shortly.

Okay, I paused Visual Studio and it looks like a threading issue actually with a lock object. I tested this a couple times and how I reproduce it is I once let it build through the Launch option without opening the Output Log. It went through successfully and no lock-up. But once I started the Launch process and immediately trying to copy text from the window, sure enough it froze up. Here is where it’s getting held up…

TextStoreACP.cpp - Line #195
*phrSession = AdviseSinkObject.TextStoreACPSink->OnLockGranted(LockManager.LockType);

It’s not advancing beyond this point and seems like its waiting for a lock to resolve but it’s not happening. Hope this helps and take it easy.

Hi, thanks for looking info this.

For your reference, this issue was also reported here, and we’ve found the cause to be the same line as you’ve pointed out above.

Do you have any input methods connected other than your keyboard and mouse, eg, a graphics tablet?

Hey Jaime! So as far as input devices go, I usually have connected to my PC an Xbox One controller, Saitek X52 Pro Flight System, Oculus DK2, and yes, a Wacom Intuos Pro Tablet :wink: I’m guessing the issue was related. Glad to see the issue was also previously reported. I haven’t encountered it since w/ 4.5.1 or 4.6. Thanks Jamie!