demostenes Posted April 9, 2019 Share Posted April 9, 2019 After unigine random crash (2.7.3.0), I wasnt able to start editor, it always crashed just after start, before asset check. Error in log was following: 21:38:51 World loading "db/db.world" 270ms 21:39:01 Memory::allocate(): Can't allocate 108454972320 bytes But start in debug mode was OK, so I ve found out, that crash corrupted shader cache. After deleting this file it started properly. Question is, if it possible to somehow prevent this, but at least this report can help other users what to do in such case. Link to comment
morbid Posted April 10, 2019 Share Posted April 10, 2019 Is corrupted cache file lost? Any hints on how to reproduce this? Probably crash was caused by shader compilation but's just a guess. Maybe you remember a location where it crashed? Thanks. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
silent Posted April 10, 2019 Share Posted April 10, 2019 Hi Jirka, It's recommended to remove all the shader cache files before the upgrade to the new engine version. So, if you plan to switch to 2.7.3.1 you will need to remove all the *.cache files first. Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
ExBemined Posted April 10, 2019 Share Posted April 10, 2019 We had similar issues with script cache getting corrupted (not even with a Unigine upgrade), very annoying indeed as it crashes without a decent error message and you spend some time debugging before you, as a last resort, try to delete all cache files and it's magically fixed. No idea what would trigger it, but we had it on multiple occasions on multiple computers with both script and shader cache files. Link to comment
demostenes Posted April 10, 2019 Author Share Posted April 10, 2019 (edited) 7 hours ago, morbid said: Is corrupted cache file lost? Any hints on how to reproduce this? Probably crash was caused by shader compilation but's just a guess. Maybe you remember a location where it crashed? Thanks. I ve deleted it. Probably no way to reproduce, it was some random crash related to asset operation (these are happening quite a lot), not some fixed world location... If this happens again, I will keep the cache and send it to you. Edited April 10, 2019 by demostenes Link to comment
Recommended Posts