I’m sorry you’re seeing these issues and we are more than glad to help as well. I understand the frustration that not all question on AnswerHub will be answered by the support team or Epic staff, but those that are crashes and bugs that are posted in the bug reports section and the installation and setup section take priority. These are assigned out daily during our work week and typically see a quick response and resolve rate. While the resolution may not always solve your problem immediately, especially if it’s a bug that needs developer attention, we do strive to do our best to get you back to developing your projects and games.
We do request a lot of issues to be posted on AnswerHub because they can be assigned to one of the support staff and we can track the issues progress more readily.
I’m curious about this issue with the ram being eaten up like that. Would you mind linking the AnswerHub post if you’ve made one? Also, you mentioned the asset that provoked this was available in the community content section. Can you provide a link to that post as well. This seems extremely odd that an asset is causing the ram to increase that much that rapidly.
Yeah I was pretty shocked to see it happen, never seen anything like it up until now. I sent a message to the creator of the assets a few minutes ago, but have not heard back yet. The assets don’t show up in the Content Browser at all, just the folders, and the RAM usage is going up while “Discovering Assets”.
I will post an AnswerHub report shortly and leave the link here for you. I wanted to have all the info first, but you can find the assets here:
Loading them in on version 4.6.1 (from the launcher build of the engine) in my project causes it to happen, I’ll put together a full report on it asap.
I’ll take a look at it when I’m back in the office on Monday. I did have the editor freeze while discovering assets the other day. I inadvertently migrated some content from a newer build to an older build project. I didn’t look at the memory usage and force closed the editor.
Did this get fixed? I renamed and moved some assets today in order for the names to conform to our team’s naming convention, and now I have the same bug - editor crashes on start, trying to allocate 18446744073709551614 bytes (17179869184 GB).
My suggestion is to never refactor anything. Most of my blueprints do not open issues resulted because of renames or changing something from a class to a struct or vice versa. I’ve noticed the rename stuff has gotten better but their are still issues. There needs to be a method or tool for refactoring that accounts for c++ code and blueprints at the same time.
The only solutions I’ve found is either reverting the code or rebuilding the blueprint. Unfortunately
There are a number of refactoring tools possible via your DefaultEngine.ini file that allow most types of C++ class, function, or variable moves or renames to be handled gracefully in Blueprints, but it sounds like CodeSpartan’s issue is moving assets not C++ code.
@CodeSpartan: Did you move files in the editor via Content Browser or did you do it via Explorer/Finder? It is generally unsafe to move .uasset files around outside of Unreal, as the asset references will be broken. If you do it in the editor, it will leave behind object redirector assets for anything unloaded that couldn’t be fixed up to follow. You can then fix up those redirectors to get rid of the tiny .uasset files that contain them after you are done resaving other content that was referencing them. However, ideally a broken asset reference still shouldn’t crash any of our built in types, so the icky serialization crash you posted above sounds like a real bug.
As Michael said, the crash itself is definitely a bug and you should be getting a warning message instead. If you go to the answerhub and post a bug report with the log file from the crash, we can investigate the root cause and have it fixed. Please link us to your answerhub post so that we can have it looked into asap
I’ve put a custom object (level) down, when i’m placing textures 4 out of 5 times it crashes with an error report. It’s driving me insane because i can’t finish a single level with this happening. Getting to the point of thinking of switching engines
Can you please file a bug report for this on answers.unrealengine.com and also include the crash report and log file. Make sure to include details about what version you are using and the steps you take to reproduce this crash.
If you post a link to it, I can make sure it gets looked into. Thanks for the report!
The forums will mess up callstacks with smilies and such, so it’s best if you go to the AnswerHub to fill out a bug report. Include that information and also attach your log file so we can investigate it further and make sure it gets looked into.
Can’t you just post it in the (code) (/code) tags? I’m pretty sure that gets rid of smilies in the callstacks. Then again, the odd smiley is never a bad thing when your looking through lines and lines of what appears to be a foreign language
Fixed It!!! UE4 wasn’t happy with me imported a big object in .obj format. Importing in fbx fixed the problem, also cut the level up into pieces. It seems putting textures directly on the object rather than going onto the object details and changing them there helps aswell.
I also have many crashes only on editing mode, I have a macbook pro 2012 10GB RAM Nvidia 680M with 512MB, I only want to make mobile content focused on IOS but Unreal Editor is really TOO unstable at least on OS X. I’m tired of restart the editor again and again. Another thing while I have opened the editor this consume 120% of the CPU making my MBP a toaster even if a don’t do nothing only with the editor opened. This is really a huge disappointment, any way I WILL RETURN TO UNITY 3D.