You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the cmdline samples, at the end of the main function, owlContextDestroy or other release related functions were called. But in the interactive samples, Release related functions were omitted. Should owlContextDestroy be called?
The text was updated successfully, but these errors were encountered:
In theory, yes, it would certainly be "cleaner" to do that - but for the samples it probably doesn't make much difference. When an app terminates, all the data structures allocated by OWL will automatically get released back to the OS, anyway, so it doesn't make much difference whether we do so or not.
The reason OWL still has these functions is that for some applications the user may want to release all the OWL-allocated resesources but not yet terminate the app itself - maybe even do that several times in a loop (say once per frame rendered), so it's important that OWL has some functions to reliably release all data - but for what happens after a sampler terminates it won't do much of a difference.
In the cmdline samples, at the end of the main function, owlContextDestroy or other release related functions were called. But in the interactive samples, Release related functions were omitted. Should owlContextDestroy be called?
The text was updated successfully, but these errors were encountered: