|Message: Re: thread local singleton memory leak?||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I think there is a misunderstanding. The memory-leak indicated in the documentation regards the use of singletons (thread-local or not) created on the heap, with respect to the stack.
The new utility we have introduced solves this problem.
However it is true that in our source code there are still (too many) "old style" singletons that cause a memory leak. However please consider that, by their nature, singletons exist in one and only one instance (possibly per-thread) during the full life-time of the application. Thus we can consider this as a kind of "minor" memory leak, because the memory is allocated once and freed at the exit of the application (without calling the object destructor). I recognize, however, that this is a bad design, and we are trying to improve the code.