U++ forum: Welcome to the forum

Search on this site

Search in forums

Home » Community » Newbie corner » CTRL + C = 659 Heap leaks

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: CTRL + C = 659 Heap leaks [message #52046 is a reply to message #52042]

Thu, 11 July 2019 16:42

Novo
Messages: 1430
Registered: December 2006

Ultimate Contributor

mirek wrote on Thu, 11 July 2019 04:22

So, this is console application in POSIX and you are pressing Ctrl+C to terminate it. AFAIK, Ctrl+C just calls exit, which is what is causing the leaks, as 'mybot' never gets destroyed.

Ctrl+C sends SIGINT, which causes "soft" termination of an app (unlike SIGKILL). It does all cleanup job for the process including stack unwinding (at least in x64 Linux).

Proof:
Memory leak report is a result of a call to UPP::MemoryDumpLeaks(), and it is called by

MemDiagCls::~MemDiagCls()
{
	if(--sMemDiagInitCount == 0)
		UPP::MemoryDumpLeaks();
}

So, stack gets unwinded, but in case of Xemuth memory doesn't get deallocated.
This is a bug with Xemuth's code. Embarassed

Regards,
Novo

Report message to a moderator

[Message index]

		CTRL + C = 659 Heap leaks By: Xemuth on Wed, 10 July 2019 21:05
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 06:06
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 09:36
		Re: CTRL + C = 659 Heap leaks By: Oblivion on Thu, 11 July 2019 09:57
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 17:10
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 10:10
		Re: CTRL + C = 659 Heap leaks By: mirek on Thu, 11 July 2019 10:22
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 16:42
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 00:15
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 00:18
		Re: CTRL + C = 659 Heap leaks By: Novo on Fri, 12 July 2019 00:46
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 09:44
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 09:55
		Re: CTRL + C = 659 Heap leaks By: Novo on Mon, 15 July 2019 06:15
		Re: CTRL + C = 659 Heap leaks By: mirek on Mon, 15 July 2019 08:17
		Re: CTRL + C = 659 Heap leaks By: Novo on Mon, 15 July 2019 17:16
		Re: CTRL + C = 659 Heap leaks By: mirek on Mon, 15 July 2019 19:35
		Re: CTRL + C = 659 Heap leaks By: Novo on Mon, 15 July 2019 20:18
		Re: CTRL + C = 659 Heap leaks By: mirek on Tue, 16 July 2019 00:11
		Re: CTRL + C = 659 Heap leaks By: Novo on Tue, 16 July 2019 02:11
		Re: CTRL + C = 659 Heap leaks By: mirek on Tue, 16 July 2019 09:38
		Re: CTRL + C = 659 Heap leaks By: Novo on Wed, 17 July 2019 18:44
		Re: CTRL + C = 659 Heap leaks By: mirek on Wed, 17 July 2019 20:25
		Re: CTRL + C = 659 Heap leaks By: mirek on Wed, 17 July 2019 23:04
		Re: CTRL + C = 659 Heap leaks By: Novo on Wed, 17 July 2019 23:46
		Re: CTRL + C = 659 Heap leaks By: mirek on Tue, 23 July 2019 09:36
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 10:28
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 10:30
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 22:13
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 22:24
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 22:31
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Fri, 12 July 2019 09:28

Previous Topic:	How i can play a sound?? wav,mp3,ogg,aiff????
Next Topic:	Filtering an ArrayCtrl

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Jul 05 21:35:41 CEST 2025

Total time taken to generate the page: 0.03444 seconds