Posted by slajar on
URL: https://forum.jogamp.org/low-memory-problems-causes-a-crash-tp4032466p4032471.html

well, not really. There is actually just one external window created and I have three (okay now four) contexts. The problem is, in case I am running on 32 bit with Xmx1024M we only have 512MB left for entire 32 bit software programs. That means if there is something running pretty big I am getting very fast to a low memory problem.

I can handle java heap insuffictency and I can handle native memory allocation problems in my own native code as well. This is not problem. But jogl doesn't handle it seems it relies on the driver and in my case the Nvidia driver crashed ;)

Having an DebugGL option is not really an option since the crash happens and the user gets frustated. How does he know he should start with DebugGL? We are in end-consumer range products, so it is not easy to explain what happens here and it is nearly impossible to write it in a documentation ;)