Your message dated Mon, 3 Oct 2005 23:50:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line afterstep: Pager segfaults at startup when many windows open
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 25 May 2002 09:06:15 +0000
>From [EMAIL PROTECTED] Sat May 25 04:06:15 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mintaka-dsl.utu.fi [130.232.36.179]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17BXV8-0007sQ-00; Sat, 25 May 2002 04:06:15 -0500
Received: from juhaj by mintaka-dsl.utu.fi with local (Exim 3.35 #1 (Debian))
id 17BXV7-0000wp-00; Sat, 25 May 2002 12:06:13 +0300
From: "Juha Jäykkä" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: afterstep: Pager segfaults at startup when many windows open
X-Mailer: reportbug 1.50
Date: Sat, 25 May 2002 12:06:13 +0300
Message-Id: <[EMAIL PROTECTED]>
Sender: =?iso-8859-1?Q?Juha_J=E4ykk=E4?= <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Package: afterstep
Version: 1.8.11-4
Severity: normal
The Pager module eats up a lot of memory (~500 MB) and eventually segfaults
when it is started
on a desktop with many windows already open. Usually this would happen when
afterstep is
recycled or some .Xsession script open a lot of windows before afterstep is
started. Apparently the
windows need to take a lot of memory, too, since just opening a huge number of
aterms does not make
Pager crash. Trying a lot of big pictures helps it crash.
I actually ran gdb on Pager, but seem to have lost the output somewhere; the
segfault came from
some X library.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux betelgeuse 2.4.17 #1 Sat Feb 2 00:10:15 EET 2002 i686
Locale: LANG=C, [EMAIL PROTECTED]
Versions of packages afterstep depends on:
ii imagemagick 4:5.4.5.1-1 Image manipulation programs.
ii libc6 2.2.5-6 GNU C Library: Shared libraries an
ii libjpeg62 6b-5 The Independent JPEG Group's JPEG
ii libpng2 1.0.12-3 PNG library - runtime
ii librplay3 3.3.2-8 Shared libraries for the rplay net
ii menu 2.1.5-10.1 provides update-menus functions fo
ii perl 5.6.1-7 Larry Wall's Practical Extraction
ii xlibs 4.1.0-16 X Window System client libraries
ii zlib1g 1:1.1.4-1 compression library - runtime
---------------------------------------
Received: (at 148129-close) by bugs.debian.org; 18 Oct 2005 18:03:23 +0000
>From [EMAIL PROTECTED] Tue Oct 18 11:03:23 2005
Return-path: <[EMAIL PROTECTED]>
Received: from hansolo.ghnet.pl (vox.robbo.home) [83.175.176.193]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ERvo3-0001q4-00; Tue, 18 Oct 2005 11:03:23 -0700
Received: by vox.robbo.home (Postfix, from userid 1000)
id 97E8BE2B90; Mon, 3 Oct 2005 23:50:09 +0200 (CEST)
Date: Mon, 3 Oct 2005 23:50:08 +0200
From: Robert Luberda <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: afterstep: Pager segfaults at startup when many windows open
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Linux
X-Best-Team: Mutt & Vim
Organization: Debian
User-Agent: Mutt/1.5.11
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Source: afterstep
Source-Version: 2.00.04-1
Hi,
The Pager module has been rewritten for the 2.0 series of afterstep, so
I assume the bug is gone and I'm closing the bug report.
If you can reproduce the bug with afterstep available in current sarge or sid,
please reopen the report.
Best Regards,
robert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
