Cant allocate crash

[demostenes]

Just by flying over terrain I sometimes receive error like this (unigine 2.1.1):

 

Unigine fatal error: SystemAllocator::allocate(): can't allocate 100712486 bytes

Shutdown
AL lib: (EE) alc_cleanup: 1 device not closed

 

It wasnt happening before.

 

 

 

[silent]

Hi Jirka,

 

We don't have any issues currently opened in our bug tracker with such error (flying over 256x256 terrains is OK).

Is it possible to get a test scene? You can upload it (zipped) to our FTP server:

• ftp://files.unigine.com
• user: upload
• password: uSh3aihu0ja5

We still have time to fix the bugs before the 2.2 SDK Update.

 

If you also can specify the reproduction steps and system specs it will surely help us to get to the root of this issue much faster.

 

Thank you!

[demostenes]

Hi,

 

well, reproduction will be complicated, It is happening only in our main project (big terrain, forests, cities....) and it is very random. I will try to run editor in debug mode, maybe there will be more info. I will also try if this is happening in washignton, or similar demo.

[silent]

Hi Jirka,

 

We have about 15 GB free space left on FTP server currently. How large is your project? Probably, you can just zip it (even with no compression) and send to ftp? Our QA team will try to catch this crash alongside with you. 

Thanks!

[demostenes]

Our project has 32GB, but I ve managed to reproduce it on Portangeles demo (2.1.1). Just run 32bit version of editor, it will probably crash during start:

 

http://www.endor.cz/demo/port.png

 

I have Windows 10, 16GB of RAM. Reason why I noticed this now is that I was accidentally running on 32bit version, so this memory leak can be there for long time.

[binstream]

32 bit applications can not operate with more than 4 GB RAM even theoretically (for Windows the limit is even lower).

Please use 64 bit builds for large projects.

[demostenes]

32 bit applications can not operate with more than 4 GB RAM even theoretically (for Windows the limit is even lower).

Please use 64 bit builds for large projects.

 

I know. But application shouldnt crash. Can be slow, can swap a lot, but shouldnt crash. 64bit version only hides the problem and it is only matter of time, when it will appear there also.

[silent]

Hi Jirka,

 

Devs will surely take a look at this issue. We agree that crashing is not an option in this case.

 

Sorry for the inconvenience caused.

[demostenes]

Great, thanks.

[demostenes]

Any progress? It is not critical, since 64-bit as workaround works fine, but it still means, there are memory issues...

[silent]

Hi Jirka,

 

Sorry, but this issue is still in the waiting list :( For large projects with a lot of content it is better to use x64 version.