From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-142843-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 7C5391381F3
for <garchives@archives.gentoo.org>; Mon, 26 Nov 2012 10:24:00 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EB20421C0D7;
Mon, 26 Nov 2012 10:23:46 +0000 (UTC)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id CBA2D21C001
for <gentoo-user@lists.gentoo.org>; Mon, 26 Nov 2012 10:22:37 +0000 (UTC)
Received: by mail-wi0-f171.google.com with SMTP id hn14so2479400wib.10
for <gentoo-user@lists.gentoo.org>; Mon, 26 Nov 2012 02:22:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=from:reply-to:to:subject:date:user-agent:references:in-reply-to
:mime-version:content-type:content-transfer-encoding:message-id;
bh=CM+nq14fHgt+EwGFZ8saKZm8igsWH12iUKzP56X7nwo=;
b=u2gNDQoof78DxF8pLVhR9Jl6NxseqtTlqBZSxS6T7x3gV40rW/OEFdFqnT2uuVV32g
RcyDh0yiXIfPrFtgam8m/7vQANDLuqLUGtO3xXpo3NGLk8m3KcyPFGTB6FhexdRFO6CP
AgQjnaFqqEvJGMG8WfJaykaui+S//rTi/dY+hpKm6nlazrNGr1+N2OfbdHye9ow5bTQQ
zo2s80O8wMl/Z2Yhoe3YDUUcDOi7+j+6ee4UTNdv6AAjeW7mVcZZx5c0nfzsoD+KwF1f
U47FjqkNtrPamBt5zoBL3dyddIy5YGf99X2knqc843jL3MSSkbT62gReZdcMKicl8qQO
Ngjw==
Received: by 10.216.227.137 with SMTP id d9mr3839487weq.205.1353925356490;
Mon, 26 Nov 2012 02:22:36 -0800 (PST)
Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230])
by mx.google.com with ESMTPS id i2sm20478502wiw.3.2012.11.26.02.22.34
(version=SSLv3 cipher=OTHER);
Mon, 26 Nov 2012 02:22:34 -0800 (PST)
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Debug memory leaks in X server
Date: Mon, 26 Nov 2012 10:22:17 +0000
User-Agent: KMail/1.13.7 (Linux/3.5.7-gentoo; KDE/4.9.3; x86_64; ; )
References: <50B33CCB.7060405@binarywings.net>
In-Reply-To: <50B33CCB.7060405@binarywings.net>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="nextPart1706916.BE9VQT8hlT";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201211261022.36407.michaelkintzios@gmail.com>
X-Archives-Salt: 41335fbb-f2e6-418a-a27f-1ae73ddfb925
X-Archives-Hash: 4653725c7f188524468cdb0e817ddc08
--nextPart1706916.BE9VQT8hlT
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
On Monday 26 Nov 2012 09:56:27 Florian Philipp wrote:
> Hi list!
>=20
> I have a suspicion that viewing certain PDFs in okular causes X server
> to leak memory. Currently it is using 1.8 GB after 3 days uptime. Has
> anyone else observed that? Is there a way to inspect X server's memory
> usage?
I have noticed that okular recently started breaking into a sweat when it=20
renders pdf files. Even a four page document with a bit of colour and=20
graphics seems to push the cpu:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
16387 michael 23 3 466m 52m 30m S 102 1.3 0:36.88 /usr/bin/okular
In case someone can interpret the content of the file:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
$ mupdfinfo Downloads/E016378510.pdf=20
Downloads/E016378510.pdf:
PDF-1.4
Info object (18 0 R):
<<
/CreationDate (D:20121126030121-05'00')
/Subject <>
/Author <>
/Creator (PlanetPress Watch)
/Keywords <>
/Producer (Distiller)
/ModDate (D:20121126030123-05'00')
/Title (CONFIRMATIONS)
>>
Pages: 4
Retrieving info from pages 1-4...
Mediaboxes (1):
1 ( 21 0 R): [ 0 0 612 792 ]
=46onts (2):
1 ( 21 0 R): TrueType 'FIBAKI+GillSans' (23 0 R)
1 ( 21 0 R): Type1 'GillSans-Bold' (28 0 R)
Images (7):
1 ( 21 0 R): [ DCT ] 1125x1050 8bpc DevGray (31 0 R)
1 ( 21 0 R): [ DCT ] 2550x3300 8bpc ICC (32 0 R)
1 ( 21 0 R): [ Flate ] 481x164 8bpc ICC (33 0 R)
2 ( 1 0 R): [ DCT ] 2550x3300 8bpc ICC (4 0 R)
2 ( 1 0 R): [ DCT ] 1125x1050 8bpc DevGray (5 0 R)
3 ( 6 0 R): [ DCT ] 2550x3300 8bpc ICC (9 0 R)
4 ( 10 0 R): [ DCT ] 2549x3300 8bpc ICC (13 0 R)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
Once rendered, the CPU goes down to normal levels. The problem does not se=
em=20
to occur when the pdf is just text, i.e. no photographs, or complex graphic=
s=20
in it.
Other than the various top apps, perhaps you can try lsof?
=2D-=20
Regards,
Mick
--nextPart1706916.BE9VQT8hlT
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEABECAAYFAlCzQuwACgkQVTDTR3kpaLaIgwCfea/tD0yUCydqUH5so9LwuiMa
jcQAniPIRABn9hJ9MQa/gdMNlhludzR6
=i6is
-----END PGP SIGNATURE-----
--nextPart1706916.BE9VQT8hlT--