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 » WebSSL memory leak problem.
Re: WebSSL memory leak problem. [message #26635 is a reply to message #26620] Mon, 17 May 2010 17:10 Go to previous messageGo to previous message
Oblivion is currently offline  Oblivion
Messages: 1221
Registered: August 2007
Senior Contributor
dolik.rce wrote on Sun, 16 May 2010 19:59

Oblivion wrote on Sun, 16 May 2010 17:42


I've successfully installed the latest stable release (2361-lucid-i386) of upp via ubuntu "stable" ppa yesterday. But I'm getting heap leaks with the WebSSL package all the time.


Hi Oblivion,

Glad to hear the PPA works Smile

I can't help you with the memory leak, but I know how to fix the valgrind. The command line syntax was apparently changed lately. Quick fix (in ide/Valgrind.cpp):
void Ide::Valgrind()
{
	if(!IsValgrind())
		return;
	static String ValgrindLogFile;
	if(IsNull(ValgrindLogFile)) {
		StringStream ss;
		CreateHostRunDir()->Execute("valgrind --help", ss);
		String txt = ss;
		if(txt.Find("--log-file-exactly") > 0)
		   ValgrindLogFile = "--log-file-exactly=";
		else
		   ValgrindLogFile = "--log-file=";
		if(txt.Find("--xml-file") > 0)		// Added
		   ValgrindLogFile = "--xml-file=";	// Added
	}
...
But this requires recompiling theide... If you don't want to do that, I would recommend you to use nightly PPA. I believe someone will commit this or better fix in one or two days.

Best regards,
Honza




Hello Honza,

I've switched to the nightly PPA, probably it'll be better that way.

By the way, I forgot to thank you for your efforts on putting the upp in a PPA Smile

Nice Job!


Quote:


I've posted about the WebSSL memory leak before. In short, it is this line:

CRYPTO_set_mem_functions(SSLAlloc, SSLRealloc, SSLFree);

If you comment it out there shouldn't be a memory leak warning anymore, even though it is actually still there.

For a permanent fix, all the correct openssl unload functions should be called. I will check it out myself later, but for those in a hurry; see http://www.openssl.org/support/faq.html#PROG13 for more information.



Thanks for the information phirox, I'll check it asap.

Regards


 
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: CoWork tidy up
Next Topic: SSL patch
Goto Forum:
  


Current Time: Wed Aug 06 09:51:12 CEST 2025

Total time taken to generate the page: 0.03650 seconds