You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The decompression routine used to open a navmesh file will dynamically resize the output buffer every block of memory that is read. This leads to a large number of allocations, potentially exhausting the available memory pool if it is heavily fragmented.
The text was updated successfully, but these errors were encountered:
Tries to prevent out-of-memory errors when loading nav mesh.
Introduce v5 mesh header which adds the following fields to the mesh file:
- header size (#104)
- decompressed size
The header size is used for forwards compatibility, in case we want to add
additional optional fields to the header in the future.
The decompressed size is so that we know how big the mesh data is. If we
don't have the decompressed size (v4 header) then we will decompress the
data twice - once to determine the size of the buffer.
This is all to fix the large number of allocations that are occurring in
the buffer because we don't know how large it should be.
The decompression routine used to open a navmesh file will dynamically resize the output buffer every block of memory that is read. This leads to a large number of allocations, potentially exhausting the available memory pool if it is heavily fragmented.
The text was updated successfully, but these errors were encountered: