alex.dovgodko Posted September 1, 2010 Posted September 1, 2010 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.
monitorius Posted September 3, 2010 Posted September 3, 2010 Maybe this problem is related to https://developer.unigine.com/forum/topic/51-memory-leak/
Guest extaliones Posted September 6, 2010 Posted September 6, 2010 Hello, Please, upload the screenshots with the error message.
Guest extaliones Posted September 7, 2010 Posted September 7, 2010 Hello, please, upload the following information: - log file - OS - video drivers version
alex.dovgodko Posted September 7, 2010 Author Posted September 7, 2010 Hello, please, upload the following information: - log file - OS - video drivers version ftp://ftp.wnet.ua/Games/synpub/logs.rar System: Windows 7 (build 7600) 32bit Unfortunately we have no info on user's drivers version (may be it would be better to log the drivers version?).
Guest extaliones Posted October 13, 2010 Posted October 13, 2010 We fixed this problem, in the next update it will be available.
Recommended Posts