Date: Mon, 15 Sep 2014 05:39:25 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 170690] x11-servers/xorg-server eats memory Message-ID: <bug-170690-8047-x8yXe1PG36@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-170690-8047@https.bugs.freebsd.org/bugzilla/> References: <bug-170690-8047@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-170690-8047-x8yXe1PG36>