bug #103
finalize function needed to prevent minor memory leaks
| Status: | proposed | Start date: | 08/23/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
We provide the last error as text and number. The error must be execution thread related.
When implementing as thread local storage the destructor for the main thread must be called
some-when. But it is not specified how long the error must be available. Hence the
error is stored until the application is quited. This "memory leak" is very minor since
it is just one string (we need allocated strings because of dynamic error messages).
Nevertheless memory leaking checking tools generating issues which really should be
prevented.
Just to be noted so that can be handled by language bindings on the top maybe.
History
Updated by Peter Tröger about 9 years ago
Wouldn't it be wise to get rid of this information on session closing ? This is one of the reasons why we added the shutdown procedures ...
Updated by Peter Tröger about 9 years ago
- Status changed from submitted to proposed
Updated by Peter Tröger about 8 years ago
- Project changed from DRMAAv2 C Binding to DRMAAv2 Root Specification
Updated by Peter Tröger about 8 years ago
- Project changed from DRMAAv2 Root Specification to DRMAAv2 C Binding
Updated by Peter Tröger about 8 years ago
- Status changed from proposed to final review
The OGF-42 meeting decided that the C language binding should specify an additional exit() function on global scope. This method could implement the free'ing of the mentioned data structures before application termination.
Updated by Peter Tröger over 7 years ago
- Status changed from final review to proposed
Still under discussion, since an "atexit()" handler registered by the implementation would also solve that.
(Other formats not available in this archive.