Christopher Bowman of Wayport in the last few weeks has helped identify two memory leaks, one [1] in nsoracle, and another [2] in nsopenssl. Here’s the commit mail of Jeremy Collins committing Christopher’s patch to nsoracle. I’m in the process of creating a reproducible test case to verify his patch to nsopenssl.
So, what’s his secret? He uses PurifyPlus and apparently it clued him in. I’ve been hesitant to use Purify because I’ve never used it before; I’ve always used a free tool called Valgrind. Since I’ve been hunting this leak in nsopenssl for the past several months with little luck, I’ve decided it’s time I really got familiar with Purify and add it to my bag of tricks. Thanks a lot, Christopher, for showing me the value of Purify.
This might explain why folks like Janine Sisk and Andrew Grumet are still seeing memory leaks, if they’re using both nsoracle and nsopenssl on their servers. Hopefully soon, we’ll find out if their leaks have gone away or not.








November 19th, 2009 at 8:35 pm
xy: If you tell me what distribution and version you're interested in, I can try building x86_64 binaries.
November 19th, 2009 at 8:22 pm
Ash: You're right, that's the only actual meaningful measurement - one person's performance before and after. It makes sense that Dvorak ...
November 19th, 2009 at 11:35 am
Has anyone successfully created a x86_64 build of convcharcount.la and convcharcount.so? I'd love to use this plugin, but not ...
November 19th, 2009 at 4:01 am
[...] The original posting is from Dossy’s Blog: What is GIMP’s equivalent of Photoshop’s Median filter? [...]
November 19th, 2009 at 1:30 am
I think the only way to solve this argument is for as many people as possible to list their typing ...