cancel
Showing results for 
Search instead for 
Did you mean: 

Logspam with Allocations after update to Oculus Integration 16 (Unity 2019.3.12)

jashan
Protege
I'm not perfectly sure which version of the Oculus Integration we're currently using but it's either 14 or 15. Today, I tried updating to Oculus Integration 16.0 and after the update, I'm getting massive logspam, like this:

Info: Allocation of 4682 bytes at 000002B7000E1770
Error: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 4682
Warning: Internal: Stack allocator ALLOC_TEMP_THREAD has unfreed allocations, size 4682
Warning: To Debug, enable the define: DEBUG_STACK_LEAK in StackAllocator.h. This will output the callstacks of the leaked allocations

Directly after installation of Oculus Integration 16.0, before even updating OVRPlugin:

Allocation of 4749 bytes at 000001FF81283240
Allocation of 4750 bytes at 000001FF8127F3E0
... 4757, 4755, 4744, 4748, 4740, 4739 (4x)
TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 52199
Internal: Stack allocator ALLOC_TEMP_THREAD has unfreed allocations, size 52199

I can "fix" this by reverting to the previous version of the Oculus Integration via version control. With the previous version, this never happens. With 16.0, it always happens. However, I cannot repro this issue in a minimal scene. There are no stack traces that would help figure out where this is actually coming from.

Versions:
Unity v2019.3.12f1, Oculus Utilities v1.48.0, OVRPlugin v1.48.0, SDK v1.48.0.
Oculus Desktop 2.38.4 ("Legacy VR Integration")
Oculus Integration 16.0
How can I fix this?
0 REPLIES 0