Memory leak in hello world

Kagamin spam at here.lot
Sat Feb 1 01:21:47 PST 2014


On Monday, 27 January 2014 at 09:44:50 UTC, Thejaswi Puthraya 
wrote:
> ==11356== 16 bytes in 1 blocks are definitely lost in loss 
> record 1 of 2
> ==11356==    at 0x4A0645D: malloc (in 
> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==11356==    by 0x43E366: thread_attachThis (in /home/theju/tmp)
> ==11356==    by 0x43E1F6: thread_init (in /home/theju/tmp)

thread_attachThis creates an instance of Thread class for the 
main process thread during runtime initialization: 
https://github.com/D-Programming-Language/druntime/blob/master/src/core/thread.d#L1792

> ==11356== 72 bytes in 1 blocks are definitely lost in loss 
> record 2 of 2
> ==11356==    at 0x4A081D4: calloc (in 
> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==11356==    by 0x444A95: _d_monitor_create (in /home/theju/tmp)
> ==11356==    by 0x43A181: _d_monitorenter (in /home/theju/tmp)
> ==11356==    by 0x43DF19: _D4core6thread6Thread8isDaemonMFNdZb 
> (in /home/theju/tmp)

synchronized statement in Thread.isDaemon allocates a critical 
section to lock: 
https://github.com/D-Programming-Language/druntime/blob/master/src/core/thread.d#L809


More information about the Digitalmars-d-learn mailing list