"Failed Allocations. Bucket layout" problem

Hi there!
I realised Player.log contains this output:

[ALLOC_DEFAULT] Dual Thread Allocator
Peak main deferred allocation count 9
[ALLOC_BUCKET]
Large Block size 4.0 MB
Used Block count 1
Peak Allocated bytes 4.0 MB
Failed Allocations. Bucket layout:
16B: 47 Subsections = 48128 buckets. Failed count: 14323
32B: 36 Subsections = 18432 buckets. Failed count: 30716
48B: 46 Subsections = 15701 buckets. Failed count: 20727
64B: 40 Subsections = 10240 buckets. Failed count: 44752
80B: 34 Subsections = 6963 buckets. Failed count: 7120
96B: 30 Subsections = 5120 buckets. Failed count: 25542
112B: 11 Subsections = 1609 buckets. Failed count: 18292
128B: 12 Subsections = 1536 buckets. Failed count: 5997

I don’t understand what’s the exact problem and how to fix it (which memory I should increase).
I have standard memory settings. According this log I see here is not enough pre-allocated memory. Am I right?

Hello,
We just updated the documentation on this. This also contains info on what kind of patterns could indicate that there could be more optimal settings.

Mainly though: it’s not that you’re running out of memory, just that these failed allocations couldn’t use the faster bucket allocator but had to fall back on a slower one, so it’s a question of performance vs (base line) memory usage. As the documentation states, if this happens due to loading events, it’s fine, the issue is more if it occurrs during every frame as your frame rate might suffer from it.

Either way and since you applied the “Beginner” Tag, these kinda optimizations are pretty advanced fine tuning and likely unnecessary for you.

2 Likes