Quote:
Originally Posted by Groucho2004
I'm aware of how much memory these frame sizes need (more or less).
I'm not sure if you realize that the point of that script is simply to force Avisynth to run out of memory and see how it behaves.
So, the only question is why the new version behaves differently.
|
Accidental.
Now (maybe the running programs changed the memory consumption a bit) my test even did not return from a simple malloc.
While there is intensive memory swapping in the background.
So frame reservation error is caught, C++ object reservations and internals can cause C0000005 in the VC runtime, or other buffer reservations (Avisynth BufferPool for temporary buffers) can result in silent death in malloc when it cannot reserve e.g. a 2G memory area.