Simon Wittber wrote:
Does anyone have ideas on why this is occuring, or how I might
otherwise prevent memory blow out?
I don't know it this is a decent enough solution but
if I were you I would try running the SQL service
in a subshell. Within this subshell I would
terminate then restart the prog
Stephen Thorne wrote:
On Thu, 27 Jan 2005 09:08:59 +0800, Simon Wittber
<[EMAIL PROTECTED]> wrote:
According to the above post:
a) If the allocation is > 256 bytes, call the system malloc.
b) If the allocation is < 256, use its own malloc implementation, which
allocates memory in 256 kB chunks and
Simon Wittber wrote:
Does anyone have ideas on why this is occuring, or how I might
otherwise prevent memory blow out?
The first thing to check is whether you might be accidentally keeping a
reference to the result set alive somewhere.
If that's not the case, then try to find out if the result se
[Simon Wittber]
>> According to the above post:
>>a) If the allocation is > 256 bytes, call the system malloc.
>>b) If the allocation is < 256, use its own malloc implementation, which
>> allocates memory in 256 kB chunks and never releases it.
>>
>> I imagine this means that large me
On Thu, 27 Jan 2005 09:08:59 +0800, Simon Wittber
<[EMAIL PROTECTED]> wrote:
> According to the above post:
> > a) If the allocation is > 256 bytes, call the system malloc.
> > b) If the allocation is < 256, use its own malloc implementation, which
> > allocates memory in 256 kB chunks and never re
