ultramysql
ultramysql copied to clipboard
esnme
valgrind reports possible lost memory
I've used valgrind to check ultramysql and I'm seeing around 700+ bytes of possibly lost bytes. Is there a known memory leak issue? When I am using ultramysql in my app, I am seeing growing memory
Where was it allocated? It’s possible some static initialized stuff inside the Python side of it doesn’t get freed. I’m actually not sure
From: jsia [mailto:[email protected]] Sent: den 4 november 2013 02:55 To: esnme/ultramysql Subject: [ultramysql] valgrind reports possible lost memory (#43)
I've used valgrind to check ultramysql and I'm seeing around 700+ bytes of possibly lost bytes. Is there a known memory leak issue? When I am using ultramysql in my app, I am seeing growing memory
— Reply to this email directly or view it on GitHubhttps://github.com/esnme/ultramysql/issues/43.
I actually run the tests inside umysql that's where I get the possibly lost bytes. ------Original Message------ From: Jonas Tärnström To: esnme/ultramysql Cc: jsia ReplyTo: esnme/ultramysql Subject: Re: [ultramysql] valgrind reports possible lost memory (#43) Sent: Nov 4, 2013 6:27 PM
Where was it allocated? It’s possible some static initialized stuff inside the Python side of it doesn’t get freed. I’m actually not sure
From: jsia [mailto:[email protected]] Sent: den 4 november 2013 02:55 To: esnme/ultramysql Subject: [ultramysql] valgrind reports possible lost memory (#43)
I've used valgrind to check ultramysql and I'm seeing around 700+ bytes of possibly lost bytes. Is there a known memory leak issue? When I am using ultramysql in my app, I am seeing growing memory
— Reply to this email directly or view it on GitHubhttps://github.com/esnme/ultramysql/issues/43.
— Reply to this email directly or view it on GitHub. "Sent via BlackBerry from Smart"