From owner-freebsd-x11@FreeBSD.ORG Mon Sep 15 05:39:25 2014 Return-Path: Delivered-To: freebsd-x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37FD7B01 for ; Mon, 15 Sep 2014 05:39:25 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07CCEBBC for ; Mon, 15 Sep 2014 05:39:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8F5dOJl078975 for ; Mon, 15 Sep 2014 05:39:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 170690] x11-servers/xorg-server eats memory Date: Mon, 15 Sep 2014 05:39:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emz@norma.perm.ru X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 05:39:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170690 --- Comment #9 from emz@norma.perm.ru --- By the way, I can say that the problem exists on various platforms. Type QT_X11_NO_MITSHM in google and see how many people describe the problem with empty windows. One time the problem was amplified to the point where empty windows were appearing right after start (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701469), it was patched a bit, to the point where empty windows appear after several days of uptime. As about myself in particular, I don't like to reboot my desktop in the office so it stays on all the time. After a week of xorg uptime I start to see empty windows, so it looks like a leak of memory of some kind. Some Qt applications, like psi, can be cured by setting QT_X11_NO_MITSHM=1 in their ENV and restarted. This affects only Qt applications, not the GTK ones. After some point the xorg crash is inevitable. It crashes and all the process begins again. I observe this during years. The majority of users that I asked (not much though, FreeBSD on desktops isn't that popular) told me that they really cannot reproduce the problem - either because they are not using much of Qt applications, or they are rebooting their machines (laptops mostly) after some period of time. Yup, an experiment could be taken with disabling the shm extension completely. Something I plan to do, but not yet. After all, I think the shm extension should not behave like that. When this problem arises, Qt applications launched from a shell show the error messages similar or identical to the messages in the debbian pr I mentioned. -- You are receiving this mail because: You are the assignee for the bug.