jonas.maebe at elis.ugent.be
Sat Feb 13 20:51:34 CET 2010
On 13 Feb 2010, at 20:51, Nikolai Zhubr wrote:
> 13.02.2010 16:33, Jonas Maebe:
>> The heap manager is now separate per thread so it offers much better performance. Keeping track of this information aggregated for all threads would slow things down again (even if it would be done using atomic operations).
> So it is indeed not possible to obtain global status anymore?
Not with the default heap manager.
> But how would one check global heap usage then? The necessity to collect such information by iterating through all threads somehow scares me... In particular, if some thread happens to hang or dies unexpectedly. Still, is there some recommended way to estimate heap usage per application, at least approximately?
Not without implementing a custom memory manager that does this or using some OS function to obtain this information.
More information about the fpc-devel