From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Antoine Levitt Newsgroups: gmane.emacs.devel Subject: Re: Memory leak due to bidi? Date: Thu, 04 Aug 2011 18:00:04 +0200 Message-ID: <87liv9cgl7.fsf@gmail.com> References: <87y5zatz2f.fsf@wanadoo.es> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1312475437 9311 80.91.229.12 (4 Aug 2011 16:30:37 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 4 Aug 2011 16:30:37 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 04 18:30:33 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qp0oZ-00072b-Nv for ged-emacs-devel@m.gmane.org; Thu, 04 Aug 2011 18:30:31 +0200 Original-Received: from localhost ([::1]:34892 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qp0oZ-0005qY-2O for ged-emacs-devel@m.gmane.org; Thu, 04 Aug 2011 12:30:31 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:43409) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qp0oW-0005qF-9N for emacs-devel@gnu.org; Thu, 04 Aug 2011 12:30:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qp0oU-0000zf-QR for emacs-devel@gnu.org; Thu, 04 Aug 2011 12:30:28 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:47763) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qp0oU-0000zM-Cq for emacs-devel@gnu.org; Thu, 04 Aug 2011 12:30:26 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Qp0oR-0006wu-Id for emacs-devel@gnu.org; Thu, 04 Aug 2011 18:30:23 +0200 Original-Received: from cab14-1-88-177-9-245.fbx.proxad.net ([88.177.9.245]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Aug 2011 18:30:23 +0200 Original-Received: from antoine.levitt by cab14-1-88-177-9-245.fbx.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Aug 2011 18:30:23 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 36 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cab14-1-88-177-9-245.fbx.proxad.net Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:142877 Archived-At: 03/08/11 15:47, Eli Zaretskii >> From: Óscar Fuentes >> Date: Wed, 03 Aug 2011 15:16:40 +0200 >> Cc: Kenichi Handa >> >> Kenichi Handa writes: >> >> > Could you check the versions before and after my changes for >> > char-table handling? >> > >> > 2011-07-07 Kenichi Handa >> > >> > * character.h (unicode_category_t): New enum type. >> > >> > * chartab.c (uniprop_decoder_t, uniprop_encoder_t): New types. >> > (Qchar_code_property_table): New variable. >> > [...] >> >> The tip revision of my Emacs is precisely the revision you mention. So >> far no abnormal memory consumption. bidi-display-reordering is >> nil. GNU/Linux x86_64 (Kubuntu 10.10). Daily usage of Gnus, org-mode, >> magit, several programming modes and an assortment of minor modes. The >> current instance is running since 6 days ago. Previously it ran since it >> was built (07-07) for about 3 weeks. So there was plenty of opportunity >> for showing the leak. > > Thanks for the info. > > FWIW, I'm running the version that shows "the leak" on others' > machines for the last 10 days without exiting Emacs, and last time I > looked it had a 195MB memory footprint. So I suspect the leak is > triggered by some specific usage patterns. Or maybe I'm missing > something important. I couldn't find if someone tried it, so just in case, another data point : it just happened to me with (setq-default bidi-display-reordering nil)