Jump to content

SystemAllocator::allocate(): can't allocate ...


photo

Recommended Posts

Our players got often crashes with messages like:

 

SystemAllocator::allocate(): can't allocate 8988704 (8988672) bytes

(usually the amount of requested memory is no more then 10MB)

 

The crash appears usually after game location change, i.e. after some unloading resources of old location and loading resources for a new location.

We think that in case of lack of physical memory engine shouldn't crash (or exit immediately), but should use virtual memory instead. And only if there is no virtual memory available (which shouldn't happen too often), immediate exit might be reasonable.

 

Question to community: did anybody got similar crashes?

Feature request to Unigine team: to find a matter of this problem it would be nice to have a stack trace log accompanying allocator errors.

Link to comment
  • 1 month later...
×
×
  • Create New...