Java-Gaming.org Java4K winners: [ by our judges | by the community ]         
Featured games (67)
games approved by the League of Dukes 		Games in Showcase (∞)
games submitted by our members



News: Read the Java Gaming Resources, or peek at the official Java tutorials
 
    Home     Help   Search   Login   Register   
Java-Gaming.org > Java Game APIs & Engines > OpenGL Development > JOGL Development > Will jogl automaticly destroy display lists when program closes?
Pages: [1]
  Print  
  Will jogl automaticly destroy display lists when program closes?  (Read 589 times)
0 Members and 2 Guests are viewing this topic.
Offline mrcox

JGO n00b
*

Posts: 13
« on: 2006-05-23 06:11:21 »
Hi
I'm just wondering if display lists that i use in my program will automaticly be destroyed/removed from memory when the program closes, or if i have to use glDestroyLists? Usually they wouldn't, but because of java i'm just curious if the trash man does:P
Offline pepijnve

Sr. Member
**

Posts: 379
Medals: 1


Java games rock!
« Reply #1 on: 2006-05-23 08:35:49 »
As far as I know, you don't need to worry about this. The operating system is responsible for cleaning up after a process terminates.
Offline mrcox

JGO n00b
*

Posts: 13
« Reply #2 on: 2006-05-23 10:18:45 »
That was not what the guys at #opengl told me, but they said that with jogl it may be different since java has a garbage collector
Games published by our own members! Go get 'em!
Offline darkprophet

JGO Neuromancer
****

Posts: 1171


Go Go Gadget Arms
« Reply #3 on: 2006-05-23 16:37:49 »
the garbage collector works on java objects, not GL resources.

The OS/driver take care of that for you, AFAIK, no OpenGL app needs to destroy any sort of resources when exiting. Im not talking about just Display lists, textures, VBOs, shaders...etc

DP
Friends don't let friends make MMORPGs.

Blog | Volatile-Engine
Pages: [1]
  Print  
 
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.071 seconds with 18 queries.