- #Not enough memory to open illustration drivers#
- #Not enough memory to open illustration driver#
- #Not enough memory to open illustration full#
- #Not enough memory to open illustration windows 8.1#
This decreases performance, of course, but it works very conveniently.
#Not enough memory to open illustration driver#
Could you maybe shed a bit light on why the out-of-memory error happens in the first place in an OpenGL application, given that not everything is needed at once? The driver is obviously able to swap data in the background, since we are constantly using more memory than the physical memory limit of the GPU, but never at the same time. It does not make life easier for a developer, though.
#Not enough memory to open illustration full#
Thank you for your response! It makes sense that the driver or even OpenGL is not in full control of the OS and how it will handle failure cases. There’s little to do about the fact that your applied workload exceeds the capabilities of your chosen hardware, other than trying to put less burden on the graphics board memory by doing smaller things more often or use one or more workstation class boards with more VRAM which can handle the CUDA simulation and geospatial rendering you require.
The OpenGL driver is able to catch out of memory cases in the user mode part, though on the kernel mode side if there is an out of memory condition the OS detects, OS counter measures against system failures get more drastic. That’s why you get different kinds of error messages. That can be failing silently, returning a fatal error which forces the OpenGL driver to abort (your case 2), or maybe just shut down the driver.
For example if a single rendering command sent to the OS uses more resources than the OS can allocate for it inside the kernel(!) mode driver at this time, there is nothing to do about some of the consequences the OS takes.
#Not enough memory to open illustration drivers#
Some of these errors are not under the display drivers control but are coming from inside the operating system itself. The OpenGL context we request is 4.4 Core Profile, if that makes any difference.
#Not enough memory to open illustration windows 8.1#
We use recent drivers (361.75) on Windows 8.1 Professional. What good is the error reporting callback if it dies with/before the context? And, well, considering events 3 and 4, the GL_OUT_OF_MEMORY error should be thrown at some point. Why is the handling of out of memory errors so inconsistent with the Nvidia driver? The driver must not overrule the OpenGL error reporting to instantly kill the entire application. Unfortunately, the events here are sorted by increasing probability, with options 2 and 4 being a hard crash and an absolute no-go for an application. The very, very bad thing is that option 1 will almost never occur.