From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dima Kogan Newsgroups: gmane.emacs.devel Subject: Re: nxml-mode in 6th 25.1 pretest: memory leak? Date: Sat, 16 Jul 2016 20:22:01 -0700 Message-ID: <87d1mdq78m.fsf@secretsauce.net> References: <868tx14hlu.fsf@phe.ftfl.ca> <83y4514gjh.fsf@gnu.org> <864m7p4eol.fsf@phe.ftfl.ca> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1468725787 15541 80.91.229.3 (17 Jul 2016 03:23:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 17 Jul 2016 03:23:07 +0000 (UTC) Cc: emacs-devel@gnu.org To: Joseph Mingrone Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 17 05:22:55 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bOcfO-000737-GW for ged-emacs-devel@m.gmane.org; Sun, 17 Jul 2016 05:22:54 +0200 Original-Received: from localhost ([::1]:39969 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOcfN-0005GV-DX for ged-emacs-devel@m.gmane.org; Sat, 16 Jul 2016 23:22:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37150) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOceq-0005GN-3v for emacs-devel@gnu.org; Sat, 16 Jul 2016 23:22:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bOcel-000708-Sn for emacs-devel@gnu.org; Sat, 16 Jul 2016 23:22:19 -0400 Original-Received: from out5-smtp.messagingengine.com ([66.111.4.29]:54393) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOcej-0006yX-HA for emacs-devel@gnu.org; Sat, 16 Jul 2016 23:22:15 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7416120301; Sat, 16 Jul 2016 23:22:03 -0400 (EDT) Original-Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 16 Jul 2016 23:22:03 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=secretsauce.net; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=9gcLh Sm/9euH4FxWnoDhb32FlBY=; b=lPOasdiH2JMdscoP9GZBX8moDF+aCcyhHEFYN 03WyoJL/qvcCH8+j2o0GTBnAo3JAgRzRx0jh4iX4pt9I+U25xldPZdBnVxoEV3bk Ky3n9UT4t7Qh815CN/7J89CeMBjnYK1zgD3lsHDNBfRQK6/jho3+/t3trFazs5AS AmsOzk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=9gcLhSm/9euH4FxWnoDhb32FlBY=; b=dIvC7 7Q9tHUcK9qYKfkQkR9OWk6B1A3OoyBeSr47t2XNp3M4ybLKDZM2rNZV4t1jj9abg RANbuiBlebBZs0fbqun+BRIPLJSNUuKQNj9hJlG6okij9J9cIi05Aah4hJxyuRqv 0+zCDLJ+gUmsC3iq3lPThRYKQTNWsKNbPK6wv8= X-Sasl-enc: 8NkQfUUMmAbL4XrU3D5W5NuEK/Scym9YwcHn6EcRO2vY 1468725723 Original-Received: from shorty.local (50-1-153-216.dsl.dynamic.fusionbroadband.com [50.1.153.216]) by mail.messagingengine.com (Postfix) with ESMTPA id 194B1F29E1; Sat, 16 Jul 2016 23:22:03 -0400 (EDT) Original-Received: from dima by shorty.local with local (Exim 4.87) (envelope-from ) id 1bOceX-0004dD-R4; Sat, 16 Jul 2016 20:22:01 -0700 User-agent: mu4e 0.9.17; emacs 25.0.95.1 In-reply-to: <864m7p4eol.fsf@phe.ftfl.ca> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 66.111.4.29 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:205772 Archived-At: Joseph Mingrone writes: >>> Within about one minute Emacs's memory usage will go from something like 150 MB >>> to several GB, then all swap will be exhausted and the Emacs process will die. I debugged some memory leaks some months ago. If you want to dig into it, the workflow is here: http://notes.secretsauce.net/notes/2015/10/05_memory-leak-debugging-tools.html