Re: Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- From: Ivan Glinka <ivan@xxxxxxxxx>
- Date: Tue, 07 Mar 2006 00:52:11 +0000
Igor, thank you for the reply.
Igor Tandetnik wrote:
There is a helpful ReleaseBindInfo function that takes a BINDINFO and deallocates appropriately anything in need of deallocating.
That's good. I wasn't aware it existed. I changed the code and put this function to take care of all clearance (removing ReleaseStgMedium, etc), but the problem persists.
I don't see any immediate problems with your code (assuming the data does actually come as TYMED_HGLOBAL). What makes you think there's a leak?
Yes, it comes as TYMED_HGLOBAL - i see it in the debug mode
.. It is not file upload - not stream - it is just a simple POST operation.
Though this mem leak can not be detected with Borland's C++ Builder 6.0, but I do the following: my APP returns the HTML code below, which once it gets to the browser and its body is loaded, immediately fires a POST request. Thus you get lots of requests a minute. I just watch it in the Task Manager: mem usage, peak mem usage, handles and so on.
So if you replace POST by GET - everything works fine - mem is at the stable value and peak mem usage doesn't increase over time (say 10K requests are enough to make sure there are no leaks). But with POST you see the mem consumed is growing constantly. And if you put more data in the form field values - the mem consumption increases.
<!-- ********************* -->
<script type="text/javascript">
function fireload()
{
var f = document.getElementById("form1");
f.submit();
}
</script>
<body onload="fireload();">
<form id="form1" method="post" action="/">
Field 1: <input type="text" name="f1" value="123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890" />
<br />
Field 2: <input type="text" name="f2" value="123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890" />
<br />
Field 3: <input type="text" name="f3" value="123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890" />
<br />
<input type="submit" value="Submit" />
</form>
</body>
.
- References:
- Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- From: Ivan Glinka
- Re: Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- From: Igor Tandetnik
- Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- Prev by Date: Re: Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- Next by Date: Re: Capturing a button click event in Browser Helper Object
- Previous by thread: Re: Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- Next by thread: Re: Mem leak on BINDVERB_POST in Asynchronous Pluggable Protocol
- Index(es):