From nobody Mon Feb 22 14:13:54 2021 Authentication-Results: mail-b.sr.ht; dkim=pass header.d=protonmail.ch header.i=@protonmail.ch Received: from mail-40140.protonmail.ch (mail-40140.protonmail.ch [185.70.40.140]) by mail-b.sr.ht (Postfix) with ESMTPS id 01A5211EFF3 for <~eliasnaur/gio@lists.sr.ht>; Mon, 22 Feb 2021 14:13:53 +0000 (UTC) Date: Mon, 22 Feb 2021 14:13:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.ch; s=protonmail; t=1614003232; bh=8EevgRtCpvn2AN4fyca41GVnL2a8h85SmMVOfaM/W5I=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=etIdUHZC+3iuMqgQFjVhZINOutZpg6c28mV/Dvo0WiPSKlCrQQa+UnX2/+oqwhzhW nQvSMintK/tkghk+OJ3Znm7KAUMgLBc2iF0gdYNim5hNePZDEnqOC9o3J+OJIxXUrW +hjTzmok3bqht/14vAK97SZyaxsUQQIxdKWobAS8= To: Elias Naur From: Loki Verloren Cc: "~eliasnaur/gio@lists.sr.ht" <~eliasnaur/gio@lists.sr.ht> Reply-To: Loki Verloren Subject: Re: bogus destroy event caused by maximizing on linux ubuntu 20.10 Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch I have discovered that wayland in general is a pointless thing for most use= rs currently due to nvidia lack of support, and so I iterated through some alternative nvidia driver versions to see if the bug had to do with the dri= ver. Sure enough, "NVIDIA Server Driver metapackage from nvidia-driver-450-serve= r" does not have this bug \o/ w00t! Since anyway most of the users will be running on windows which is fine (an= d great work eliminating the dependencies for it!), now just a note for nvidi= a drivers on linux to suggest for 10 series use that driver as it has no issu= es and there is a known issue of 460 and 4k displays and windows taller than, not sure but I can guess it's 1080. Sent with ProtonMail Secure Email. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Monday, February 15th, 2021 at 09:11, Elias Naur wr= ote: > On Sun Feb 14, 2021 at 20:17, Loki Verloren wrote: > > > Currently the go.mod on my project refers to this build: > > > > gioui.org v0.0.0-20201229000053-33103593a1b4 > > > > and I have discovered that on Linux there seems to be some egl > > > > error occurring that seems to shut down the render loop, main > > > > trigger being to maximize the window, notably, on a 4K monitor > > > > to near 3840x2160. It also can happen sometimes just by sizing > > > > the window too tall, the vertical axis seems to be the trigger, > > > > as any amount of width doesn't seem to affect it. > > > > I tried upgrading to the latest version and it is the same. > > > > My logs show the event is triggered and thereafter the > > > > interface stops This only seems to happen on linux, 100% sure > > > > replicates on 20.10, could be others but that's all I run. > > > > This is the error here: > > > > newContext: eglCreateWindowSurface failed 0x3003 (sRGB=3Dfalse) > > > > Once this error occurs, the window becomes entirely unresponsive. > > I tried a few combinations on my Fedora 33: Sway, Gnome, Gnome on Xorg. > > All with a 4K monitor in portrait and landscape mode. I didn't succeed > > in triggering the error. > > 0x3003 is EGL_BAD_ALLOC which sounds like an out of memory condition. > > Does the error happen every time and immediately after maximizing the > > window? If you have to, say, maximize a few times or resize the window a > > bit before triggering there may be a latent GPU memory leak in Gio. > > Elias