From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: How to find memory leakage in x image code? Date: Thu, 05 Nov 2009 15:43:19 +0100 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1257432447 6197 80.91.229.12 (5 Nov 2009 14:47:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 5 Nov 2009 14:47:27 +0000 (UTC) To: Emacs development discussions Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 05 15:47:20 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N63cG-0005Gj-TR for ged-emacs-devel@m.gmane.org; Thu, 05 Nov 2009 15:47:13 +0100 Original-Received: from localhost ([127.0.0.1]:49650 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N63cG-00023C-HR for ged-emacs-devel@m.gmane.org; Thu, 05 Nov 2009 09:47:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N63Yg-0000X4-Er for emacs-devel@gnu.org; Thu, 05 Nov 2009 09:43:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N63Yb-0000TJ-Ck for emacs-devel@gnu.org; Thu, 05 Nov 2009 09:43:29 -0500 Original-Received: from [199.232.76.173] (port=52632 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N63Ya-0000T3-JR for emacs-devel@gnu.org; Thu, 05 Nov 2009 09:43:24 -0500 Original-Received: from proxy1.bredband.net ([195.54.101.71]:54507) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N63Ya-00083L-3n for emacs-devel@gnu.org; Thu, 05 Nov 2009 09:43:24 -0500 Original-Received: from ipb2.telenor.se (195.54.127.165) by proxy1.bredband.net (7.3.140.3) id 4AD3E1C0009C6754 for emacs-devel@gnu.org; Thu, 5 Nov 2009 15:43:21 +0100 X-SMTPAUTH-B2: joakvero X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlpVAAdz8kpT44qWPGdsb2JhbACJVJIGAQEBATfDWYQ9BA X-IronPort-AV: E=Sophos;i="4.44,686,1249250400"; d="scan'208";a="153791" Original-Received: from ua-83-227-138-150.cust.bredbandsbolaget.se (HELO exodia) ([83.227.138.150]) by ipb2.telenor.se with ESMTP; 05 Nov 2009 15:43:21 +0100 Original-Received: from localhost.localdomain (DIR-655.lan [192.168.200.113]) (authenticated bits=0) by exodia (8.14.3/8.14.3) with ESMTP id nA5EhJ7T004655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 5 Nov 2009 15:43:20 +0100 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116658 Archived-At: I'm using my Imagemagick patch I posted a while ago a lot to work with scanned documents. They are mostly 300dpi A4 BW djvu images. After viewing something like 100 images or so, the entire X session frequently crashes. I cant figure out where the leakage is. Killing the image buffers doesnt help. The image cache is supposed to be flushed frequently enough for X not to crash right? The basic allocation/deallocation is the same as for most other image type supports in emacs. Does someone else experience the same problem with viewing a large number of SVG images for instance? -- Joakim Verona