Happy New Year guys. I’m starting work on a new game using OS X and I’ve run into a number of consistent crashes across a couple of Macs here. I’ll group all the ones I could find together because I have a suspicion its from one bug or very similar bug across the crashes.
I am running the latest version of OS X 10.11.2 and UE4 10.0.1. One computer is a 2013 13" rMBP 8GB and the other a 2011 27" iMac 16GB.
Overall I can create most assets just fine, but I noticed a number of items will cause to editor to crash out automatically.
Here are the following instances where I can crash the editor:
Using Command+Shift+S to try and save the current level as a new level (this was mentioned as the new way to duplicate level as the Duplicate method for levelshad been removed from the editor.
Creating the following assets from the right click menu in the content browser:
Animation → Aim Offset
Animation → Aim Offset 1D
Animation → Animation Blueprint
Animation → Animation Composite
Animation → Animation Montage
Animation → Blend Space
Animation → Blend Space 1D
Also when Clicking on the + buttons under the Game Mode heading in World Settings panel
GameMode Override
Default Pawn Class
HUD Class
etc.
I believe there may be a crash when the editor tries to render the modal window, as I’m relatively certain all of these items try to display some window when creating these assets.
I also have a number of consistent hangs but perhaps I should post those as a separate ticket as they don’t crash the editor just hang it and cause the beach ball to show up on OS X.
I can provide crash dumps, logs etc. just let me know what you need.
I have also tested on 4.11p1 and can sometimes see the window before it crashes.
Do all the instances occur in a Blank project? If you have not done so, please try in a Blank Third Person Blueprint project and a Blank Third Person C++ project.
Also please provide the complete system specs for both Macs you are having this problem on:
You can find this in the Apple menu >About This Mac>More Info> Add the information from this window (serial # not necessary).
Sorry for the delay on the iMac specs. I just in the last day or so installed the latest OS X 10.11.3 beta 2 on this particular system to see if that had any effect either way. Still seeing the same issues as the rMBP / 10.11.2.
We tried to reproduce the crashing on two Macbook Pros, one running Yosemite and the other but were not able to following the repro steps you have provided here and on your other post concerning long lag times.
Both of your computer specs are right on the minimum requirements to run the engine, your MacBook Pro being slightly below spec. One test to verify that the crashes you are experiencing are hardware related would be to reduce settings that are heavy on your gpu & cpu. If reducing these settings alleviates the problems even a little bit, then the issue is most likely due to your system being slightly under spec.
Under Settings>Engine Scalability Settings> adjust these to the lowest settings:
Then, in the Viewport, uncheck all of these:
Finally, you can try downloading less graphic intensive versions of the Engine like 4.6 or 4.7 and see if these versions cause the same sort of issues.
Please try these troubleshooting steps and let us know if the engine runs better/ ceases to crash.
I have changed those settings per your request and still get the same result on both systems as before.
I have downloaded 4.7.6 on the MBP and I can now see the Create New Game Mode, Pick Skeleton, etc. windows - even if I manually set all the scalability settings to Epic.
4.7.6 still gives me the spinning beach ball as described in the other ticket.
Unfortunately 4.7.6 gives me a lot of instability and crashes in other areas. 4.10 is actually pretty solid for me so far most of the time except for the issues reported.
I just did a simple return of 0, and {NSNotFound, 0} before the GameThreadCall/GameThreadReturn blocks and the editor will correctly display the windows and let me continue on with creating the assets.
Obviously these aren’t real fixes just some preliminary testing. I’d like to look further into this but currently I have zero C++ experience and not so much OS X dev experience so I’m not super comfortable yet coming up with a real fix and a pull request. Perhaps this information could be helpful for your engineers in the mean time though.
Looking at the Crash reporter data for the last few days, three of the four crashes occurred in a custom project called “SoujiPanic” (which I assume has custom assets) and one in “MyProject.” The three crashes have unique callstacks, so they are not the exact same issue, although one shares the same issue from “MyProject.”
So, does the “SoujiPanic” share any unique assets with “MyProject?” Also can you reproduce the crash the blank Third Person Animation project? Is “SoujiPanic” the puzzle game you mentioned before and “MyProject” the Third Person Blueprint game? If not, please clarify. -The purpose of this is that we are trying to recreate the crash locally on one of our machines.
Yes thats another test project I have, it’s using a puzzle based project template with a handful of custom assets.
MyProject is a brand new Third Person project with no starter content. No sharing of assets with that other project, and no other new assets added or imported before producing the crash.
I usually create a new “MyProject” or similar when updating UE4, etc. just to make sure I’m starting from a fresh state.
I can upload the MyProject up to a public Git repo if it helps any. Maybe there is something with my local setups that is generating incorrect assets by default?
Also just testing now with a new Project I got a crash creating a new GameMode Override which was caught by the UE4 crash reporter.
In addition this attached file is for trying to create an Animation Montage, but it wasn’t caught by the UE4 crash reporter, but the built in OS X one. Maybe is has some other info that might be helpful?link text
Not a Git repo, but here is the full zipped project on Google Drive. There should be at least one crash report in your system from this project which I just created today.
Thank you for providing all the requested information. I have used your description of the crash, system specs, supplied logs, and crash reporter data to generate the following bug report: JIRA [UE-25362].
If we are able to determine the cause of the crash and are able to correct the issue, we will notify you with an update to this post regarding which release contains the fix.
