[Xitami] Memtrace.lst growing very large

[Brian Kowald]

This message is in the Windows Application log:

The description for Event ID (0) in Source (Xitami) cannot be found. The
local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE=flag to retrieve this description; see Help
and Support for details. The following information is part of the event:
Xitami error:0, Memory leak error, see 'memtrace.lst'


-----Original Message-----
From: Pieter Hintjens [mailto:ph at imatix.com] 
Sent: Monday, September 24, 2007 11:01 AM
To: Xitami Users General Discussion
Subject: Re: [Xitami] Memtrace.lst growing very large


On 9/24/07, Brian Kowald <bkowald at synergybroadcast.com> wrote:

> Can logging to memtrace.lst be turned off so it doesn't fill up the 
> hard drive?
>
> Our LRWP application is written in C and uses the SFL.

Rather than switch it off, you should fix the memory leak - it looks
like a problem in your LRWP application.  It's quite simple - the first
page of the memtrace.lst file will show the file and line number of the
allocation.  (If you don't see this, rebuild with -DDEBUG).

If you don't fix the leak, the application will eventually kill the
machine in any case.

-Pieter


--
Xitami Users Mailing List -- For Xitami support
To unsubscribe: http://lists.xitami.org/mailman/listinfo/xitami