From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Dima Kogan Newsgroups: gmane.emacs.bugs Subject: bug#21509: 25.0.50; X11 error: BadPixmap when creating first emacsclient frame; and memory leak Date: Mon, 16 Oct 2017 09:33:01 -0700 Message-ID: <878tgbvyrm.fsf@shorty> References: <877fno9w6b.fsf@secretsauce.net> <59ABD636.3070302@gmx.at> <87wp5d8y37.fsf@scrawny> <59AE5DD1.9050602@gmx.at> <87vaks8wul.fsf@scrawny> <59B39F76.2010508@gmx.at> <8760bhcbqm.fsf@secretsauce.net> <59E32D26.6030901@gmx.at> <87376kclqm.fsf@secretsauce.net> <59E462D1.5060300@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1508171666 17580 195.159.176.226 (16 Oct 2017 16:34:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 16 Oct 2017 16:34:26 +0000 (UTC) User-Agent: mu4e 0.9.17; emacs 26.0.50 Cc: 21509@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Oct 16 18:34:21 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e48L7-000277-IJ for geb-bug-gnu-emacs@m.gmane.org; Mon, 16 Oct 2017 18:34:05 +0200 Original-Received: from localhost ([::1]:34046 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e48LE-0004C9-Vn for geb-bug-gnu-emacs@m.gmane.org; Mon, 16 Oct 2017 12:34:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e48L9-0004C4-VS for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 12:34:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e48L4-0005hf-FJ for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 12:34:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:35424) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e48L4-0005hM-8Z for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 12:34:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e48L3-0003eL-TO for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 12:34:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dima Kogan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 16 Oct 2017 16:34:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21509 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 21509-submit@debbugs.gnu.org id=B21509.150817158713832 (code B ref 21509); Mon, 16 Oct 2017 16:34:01 +0000 Original-Received: (at 21509) by debbugs.gnu.org; 16 Oct 2017 16:33:07 +0000 Original-Received: from localhost ([127.0.0.1]:44105 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e48KA-0003b2-TE for submit@debbugs.gnu.org; Mon, 16 Oct 2017 12:33:07 -0400 Original-Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35909) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e48K9-0003au-En for 21509@debbugs.gnu.org; Mon, 16 Oct 2017 12:33:05 -0400 Original-Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B215021127; Mon, 16 Oct 2017 12:33:04 -0400 (EDT) Original-Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 16 Oct 2017 12:33:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secretsauce.net; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=Z6yj0fVTj/L26aZ1FDkvSmP09d2O2txHlYEIzxyF8ps=; b=jlFpTIv5 OyGt5oa1HrGqYnW7SJcHnzErGtD0No24fUpqhSRwjiXlURn6EgK7cHN9VA98e8av TpXOS1caRYk3hd+C8cu1XGvpz5F0ucSt71pqm0ucBPw5ywl8COSxC9iQHTryQiAK UXy+wns1YY6PO7E9RBw+Q8yRqZHjZFMoRD9OkYIEkQEwXvLLml3jdUkJppVKwHI0 6GPPXfU9dF83zkESV0F1CpiM+5LP7qxtTvTXbc82dGrFooW3GlmjSgfDDmR85nhF OWRIoq4eU19LlMf5DBcEmKuTUctGye8UrIxFdI+etXspNV2j8b29cPQDtRm6CkKs v1uR7sUisIR+RQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=Z6yj0fVTj/L26aZ1FDkvSmP09d2O2 txHlYEIzxyF8ps=; b=jkSaB9LJ4NEWaNX2x2+QM1yrgBpAQzFtkSB8qI9Aiwy5i bEyrl1ODKxyfFP4ZE5eKz67AFUkSJPtMz7O4hIyvRkcrOvQQYHg/Qkd/MkE3hmiM 3/bFNLvDAt+pH0snzkBjb2HtY8dukCP+Fvn2SQJkEwHfwfD3U7QXKVZCKe14xU4p 6KPBTKItCQpqk17YdLVve8svUvwlj1RuTkYIUd0XSGcOod7aQkrpNw9sOd9AulTH p8w2Hi5AYENz5zntT0tcw4xE5PrEKkfp8zfnX3q4+aN9wNYpav3pP6bG4PdeTH9C vw7LjGW3zny6dm7qS7cly991/KFez2DvGG/iCklWQ== X-ME-Sender: Original-Received: from shorty.local (guest-181.vonkarman.net [207.151.223.181]) by mail.messagingengine.com (Postfix) with ESMTPA id 599A924138; Mon, 16 Oct 2017 12:33:04 -0400 (EDT) Original-Received: from dima by shorty.local with local (Exim 4.89) (envelope-from ) id 1e48K6-0005Fn-3O; Mon, 16 Oct 2017 09:33:02 -0700 In-reply-to: <59E462D1.5060300@gmx.at> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138538 Archived-At: martin rudalics writes: > What surprises me is that both 800K cons-threshold runs apparently start > with a considerable lower memory consumption (around 20000 kB) than the > 80k and 8000k runs. Ah, that I CAN explain: it's an artifact of the way I ran the trials. For the 800k cases I'd start the emacs daemon from the commandline, and then start gathering the data and cycling the frames. For the 80k and 8000k cases I'd start the daemon, and then take an extra step: Open a single client frame to (setq gc-cons-threshold whatever) I should have started gathering the usage data before I opened this first frame, but I guess I didn't. So the memory usage plots the 800k start when no frames have ever been created, but the 80k and 8000k start after 1 frame was created. So this difference isn't indicative of anything interesting.