Hi Archie,
I believe the problem is now fixed in CVS. My test application ran overnight (twiddling the href 20-30 times a sec) with no detectable increase in the baseline heap size (this is ~1million twiddles so the heap would have grown significantly even if a single object was leaked).
Archie Cobbs wrote:
Thomas DeWeese wrote:
I've given the code a good looking over and it is hard for me to see where the leak occurs, but I am very interested in finding it. Any chance of a reproducible test case?
I'll try to come up with one as soon as time permits... hopefully it won't be too hard.
Your off the hook I have one. I didn't think I was getting anywhere but I ran my test overnight and it failed. I also think I have a fix, I'll need to run the test overnight again however.
Great! Thanks for working on this problem.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
