GNU bug report logs - #43389
28.0.50; Emacs memory leaks

Previous Next

Full log

Message #386 received at 43389 <at> debbugs.gnu.org (full text, mbox):

From: Carlos O'Donell <carlos <at> redhat.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Jean Louis <bugs <at> gnu.support>
Cc: fweimer <at> redhat.com, 43389 <at> debbugs.gnu.org, trevor <at> trevorbentley.com,
 michael_heerdegen <at> web.de, dj <at> redhat.com
Subject: Re: bug#43389: 28.0.50; Emacs memory leaks using hard disk all time
Date: Mon, 23 Nov 2020 15:04:33 -0500

On 11/23/20 2:34 PM, Eli Zaretskii wrote:
>> Date: Mon, 23 Nov 2020 21:58:28 +0300
>> From: Jean Louis <bugs <at> gnu.support>
>> Cc: Eli Zaretskii <eliz <at> gnu.org>, fweimer <at> redhat.com,
>>   43389 <at> debbugs.gnu.org, dj <at> redhat.com, michael_heerdegen <at> web.de,
>>   trevor <at> trevorbentley.com
>>
>>> Sorry, please drop MTRACE_CTL_VERBOSE=1, as it adds output to stdout
>>> which may affect the process if using pipes.
>>
>> # MTRACE_CTL_VERBOSE=1
>> MTRACE_CTL_FILE=/home/data1/protected/tmp/mtraceEMACS.mtr LD_PRELOAD=/home/data1/protected/Programming/git/glibc-malloc-trace-utils/libmtrace.so emacs >> $DEBUG 2>&1
> 
> Any reason you redirect stderr to stdout?  I'm not saying that is the
> reason for the EWW problems, but just to be sure, can you try without
> that?  The trace goes to stderr, right?  So just "2> file" should be
> sufficient to collect the trace.  Carlos, am I right?
 
No, the trace goes to the trace file specified by MTRACT_CTL_FILE.

By default the tracer is as minimally intrusive as possible.

-- 
Cheers,
Carlos.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.