Hello guys,
I sent too many crash reports when I was on 4.7.3, but this crash still happens in 4.7.5.
It happens very often when I work in blueprint editor. My repro rate - 80%. It may happens in any example project without any changes. Just open any BP graph and try to pull new node connection for creating new node.
Open BP editor;
Pull new node connection (from any other node with any type);
Crash.
My system: OS X 10.9.5
My total RAM: 16 Gb
RAM used at crash moment: 6-8 Gb
There are known stability issues with OS X 10.9.5. I just attempted to test your issue on a machine here and was not able to get any slowing or crashing. I opened up the ‘Blueprint’ example project from the ‘Learn’ tab for version 4.7.4.
You could try updating your OS X to 10.10.1 and see if your performance and stability improve. Would you also be able to provide me with your full system specifications? I.e. your integrated graphics card and your processor.
I noticed, that this crash happens not only in Event Graph. It happens everywhere in editor when tooltip appears. Before crash tooltip starts fade in animation and on 70% (approximately =) ) of animation editor stucks for a moment and then opens Crash Report Tool.
You could try updating your OS X to
10.10.1
Sorry but I can’t do it in near future.
Would you also be able to provide me
with your full system specifications?
I am still unable to reproduce the crash you are reporting. I have attempted to open multiple different blueprints in various sample projects we have on the marketplace, but with no success. Are you using the binary version (from launcher) or are you using source (GitHub) to run the engine?
Would you mind finding a single project that you can get this crash to reproduce and let me know which project it is you are testing. If you manage to reproduce the crash, would you type the tittle of this post into the comment box within the crash reporter tool so I can track down the crash?
This crash randomly causes in all example projects. In engine binary version downloaded with launcher and in compiled from source version too.
Sometimes this crash can occur very rarely (after a few hours of work) but also it can occur very often (after every project launch). It’s very difficult to predict when this might happen.
But I noticed one strange dependency - whenever this happened on my mac was running a lot of other applications: Сhrome with too many tabs, Photoshop with opened textures and etc. But my RAM has enough free space 4-5 gb.
Also, as I mentioned above:
I noticed, that this crash happens not
only in Event Graph. It happens
everywhere in editor when tooltip
appears. Before crash tooltip starts
fade in animation and on 70%
(approximately =) ) of animation
editor stucks for a moment and then
opens Crash Report Tool.
I have attempted to search for your issue in our crash reporter, but am unable to find the crash. In order to create an efficient and effective bug report, I will need to find a way to reproduce your issue on my end which seems to be a random occurrence.
My first suggestion to avoid the crash given the most recent information, would be to try and keep less applications running in the background, even though you have sufficient RAM, if you are dividing your processing power by keeping various applications open, you increase your risk of causing the editor to freeze and/or crash.
If you could, next time you experience this crash please make a comment in the box stating what you were doing at the time of the crash as well as making sure you press the ‘Send’ button at the bottom. If you do not send the crash report, then we cannot view the crash on our end to test and reproduce.
If you have any other questions, comments, or concerns please let me know.
I send the report many times. And I absolutely sure that I pressed “send” button each time =) Also almost every time I described my recent actions in the editor. It is very strange that you could not find my reports.
After doing some more digging I was able to locate your most recent crash. The good news is that the crash has to do with moving material nodes and/or building level with changed material. We have already entered a bug report in our system for this issue and has been fixed for the upcoming release of engine version 4.8.
I appreciate your patience while attempting to troubleshoot this issue, and if you have any further questions please let me know.