Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » httpRequests in secondary non-gui-main Thread (if memory leaks come from http.buffer?)
Re: httpRequests in secondary non-gui-main Thread [message #55359 is a reply to message #55330] Mon, 02 November 2020 11:57 Go to previous message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
JeyCi wrote on Sat, 31 October 2020 11:38
Klugier wrote on Sat, 31 October 2020 11:18
Without the code it will be difficult to diagnose what is causing the problem.

well... it can take time... I just saw such variable in debugger (with multiple FreeFreeFree...) when I had a memory leak... the first question is just about - does it really mean that the memory is being allocated, but not freed?..


If you see pointer pointing to "FreeFreeFree....", it most likely means that it points to the memory that was already deallocated.

In debug mode, U++ allocator fills the memory with this pattern on deallocation. Then when the same block is allocated again, it checks that the pattern is unchanged. If it is not, it would means something has written to that memory after it was deallocated, which is a sign of dangling pointer problem. In that case the app is aborted (in debug).

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Encoding URL for HttpRequest
Next Topic: Missing data in the socket
Goto Forum:
  


Current Time: Mon Apr 29 05:34:25 CEST 2024

Total time taken to generate the page: 0.04231 seconds