Cool VL Viewer forum

"Implemented a memory allocation failure detection algorithm and now react accordingly to urgently free memory (by reducing the draw distance to 64m and resetting the camera view) so to try and avoid a crash: this algorithm comes in excess of the "Memory Safety Checks" and, unlike the latter, is able to catch (some, not all, alas) fragmented virtual address space conditions that cause allocation failures even when some memory is still free. This should reduce significantly the number of virtual address space exhaustion/fragmentation related crashes."

Is there a way to turn that off? It's interfered a few times already and there was no detected memory issues.

I've long ago turned off the memory safety checks as it tended to cause more memory restrictions than not. (In fact I've been pretty well bug free for quite some time!)

Unlike the "memory safety check" which is a preventive algorithm (it checks for free memory and adjusts future memory consumptions accordingly), this new feature kicks in when memory allocation failures *do* happen: in clear language, the "times it interfered" would have been crashes without that feature.

So no, there is no way to disable it (and you should be thankful for having it since it prevents crashes and lets you a chance to relog when appropriate instead).

The memory allocation failures may happen in two cases:

• There is no virtual memory address space left (something the "safety check" helps preventing but not suppressing entirely).
• The virtual address space is so fragmented that some big blocks can't be allocated in it spite of the total "free memory" that would otherwise allow it (this is a condition that the "safety check" can't detect).

If you often encounter such memory issues, then try tuning your system and viewer settings: there are already quite a few posts on this subject in this forum...

Well that sucks because since that build, I've suffered MORE unnnecessary crashes and graphics 'roll backs' (some while filming LIVE EVENTS!!) that effectively makes the viewer totally unreliable and unusable on lower end computers (think single and double processors here).
Now I am stuck with the last stable build without this bug: v1.26.4.82. Trust me, Giant memory mapping is NOT the way to go as it WASTES more resources than it effectively handles.

*Again*, this feature helps *preventing* crashes, it does NOT cause any crash by itself !!! And there's no "giant memory mapping" involved either.

If you are not happy with my viewer, by all means, choose another !