Home » Community » Newbie corner » CTRL + C = 659 Heap leaks
Re: CTRL + C = 659 Heap leaks [message #52039 is a reply to message #52037] |
Thu, 11 July 2019 09:36 |
|
Xemuth
Messages: 387 Registered: August 2018 Location: France
|
Senior Member |
|
|
Hello Novo, Thanks for you reply.
Quote:You are, most likely, manually allocating/deallocating memory
Don't think so, I never use New or malloc.
Quote:you store pointers to polymorphic classes
In my code I use lot of Ptr of type "DiscordModule", the mother class of lot of object stored in this kind of thing :
Upp::Vector<DiscordModule*> AllModules;
I thought it come from that but by launching my code without filling that vector still result on the same huge amount of memory leak !
Quote:which do not have a virtual destructor, in a container
I tried to declare destructor -> here is definition of my class :
class SmartBotUpp{
private:
Upp::Vector<DiscordModule*> AllModules;
Discord bot;
Upp::String name="";
Upp::String token="";
void Event(ValueMap payload);
Discord* getBotPtr();
public:
...
};
and here is the destructor
SmartBotUpp::~SmartBotUpp(){
AllModules.Clear();
}
Quote:AFAIK, you can click on memory leaks in TheIDE, and it will show you where this memory was allocated. I can be wrong, I haven't seen memory leaks in my code for very very long time Rolling Eyes
How you do it ? I get all the memory leak by looking log on theIDE but it's not clickable
Quote:One interesting thing about U++ is that you almost never need to call new/delete or malloc/free. Yeah that's exactly what I'm doing. That's why I'm lost
Best regard.
|
|
|
|
|
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
|
|
|
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
|
Goto Forum:
Current Time: Fri Apr 19 14:46:51 CEST 2024
Total time taken to generate the page: 0.02209 seconds
|