We recently found a huge leak in the UE4 garbage collector, particularly rearing its head on dedicated servers for large open-world games. Servers for arena type games with short play times (<1 hour) seem to be little affected, and clients don’t see the problem much either. “Huge” is not hyperbole here – we’re talking the garbage collector alone using up to 10 GB of ram in under 24 hours of server operation!

In this article we delve into Blueprint Nativization, a relatively new feature of UE4 that offers significant performance improvements for many projects. Sadly, it often doesn't work out of the box - we've spent some time fixing and improving it for a particular project that we were working on. We have a LOT of changes to present here - some of which have already been implemented into UE4.

We found quite a large leak within Apex 3.4 (currently used in Unreal Engine 4, amongst others) - in a relatively short run of the title that we were working on, we saw over 150mb of leaked memory. Here, we present some changes that will fix this

We were seeing frequent file IO errors in relation to temporary files created during cooking (particularly when compiling shaders). Our findings for why this were happening were surprising. Here we present a clean way to fix the issues

A really small bug fix is presented here - with a lot of Trekkie banter to fluff the piece out... and why not?

The sixth part in our series looking at coding errors found by using the static code analysis tool PVS-Studio

PVS-Studio pointed us toward some code with suspiciously mixed signed/unsigned math. This was actually causing some issues - and here we tell you how to fix them

A common programming mistake is fixed here, this time in the FBX importer

The fifth part in our series looking at coding errors found by using the static code analysis tool PVS-Studio

In this post we present an optimization coming from removing some pointless null pointer checks. The way that we found this was quite interesting

When a process takes a long time to complete, it makes absolute sense to put some time limit checks in so that you're not starving other work. What you don't want to do, of course, is to have those checks slow your original task down further by any considerable amount - here, we found that exactly this was happening .. so we present a solution

Here we present several small code fixes and improvements in a nice little package

UE4's Package Versioning is a bit of a dark art for most.. here we try to remove some of the confusion around it - while, again, offering some improvements through optimization

The fourth part in our series looking at coding errors found by using the static code analysis tool PVS-Studio

The third part in our series looking at coding errors found by using the static code analysis tool PVS-Studio

We found CreateExportHash() was showing up in profiling the cooker - so we optimized it. Our findings and changes are presented here

The second part in our series looking at coding errors found by using the static code analysis tool PVS-Studio

The first part in our series looking at coding errors found by using the static code analysis tool PVS-Studio

While profiling a game's runtime, we found that 40% of memory allocations were coming from a single function. The fix/optimization involves adding a single character

We present a tiny little fix for a simple - but serious - coding error in the UE4 codebase