Unreal Editor freezes, crashes when mouse goes over a tooltip

Unreal Editor 4.7.6 on Mac OS 10.10.3 freezes, sometimes crashes, when the mouse cursor goes over a tooltip. It usually happens in a blueprint and material editors. When dragging a node, if the cursor goes over a tooltip, the editor freezes for a minute. If you try to click anywhere during the freeze, the editor usually crashes. After the first freeze, nothing like that ever happens during the current season. Tested with the Apple mouse and any USB or wireless mice.

Hello rachmiroff,

I have been attempting to reproduce the crash you are reporting on my end, but have been unable to do so thus far. If you are able to reproduce the crash in a new project, or have steps that I could follow to get the crash to occur on my end, that would be helpful for getting a fix implemented.

Could you also please provide me with your full system specifications as well as the callstack and crash logs generated from the crash. Grab all of these files, zip them into a folder and attach them to your response.

Thank you,

Here is the crash report and my system information. I also noticed that the editor does not crash when I start it from Xcode (with -debug flag and a project file path). It only happens when I start the editor from the binary directory directly or from the launcher.

link text

Hey rachmiroff,

Taking a look at your system specs and your RAM as well as your VRAM (Graphics Card Memory) is right below the minimum recommended specs. With only 4 GB of RAM and 512 MB of VRAM, your computer will have hitches and crash when running multiple tasks or somewhat heavy processing. This explains why the engine is crashing when you are dragging nodes or working within the material editor and hovering over a tooltip.

Thank you,

I actually did have 8 GB before. It was still crashing. Also, how dragging a node can be called ‘heavy processing’? No other jobs of the editor were running. Plus, it does not crash/freeze when running from Xcode. I think you guys still have a bug in Slate and it’s not related to vram or ram memory consumption.

I can still submit a bug report even if I cannot reproduce your issue. If you sincerely think there is a bug here, I do not want to ignore that fact.

Thanks,