probably not even an error we can fix. this is probably something to bring up with the appropriate driver developers, but even then may never be fixed. also note you may hit a limit at 126/127/128 or so or maybe 254/255 as xorg has a limit on client connections and last time i hit it, it was 128 clients (e will have 1 connection at least itself to start). so you'll hit a wall/limit like that that will probably be far before you hit a ram limit these days. as i said the 20/30 limit smells like a driver/gpu limit in maximum number of contexts or something similar. we impose no limit in efl and even if we did it's be per process, not globally.

Probably not getting fixed any time soon

87cf5188b466d3fa1e8c8ff7ad6d5039b28e298a should sort this.

i don't even know that we get an error or can detect it. we do things like check the return of glxcreatewindow and error out and complain what failed. it seemingly is not failing. if we don't see things failing from the glx/egl api then we can't do anything about it.

In T7097#129282, @raster wrote:

this smells here like a video driver issue - like there are a limited number of "contexts" (video ports) for output rendering and once you hit the limit things fail. that's what it smells like at any rate... so either a hardware or driver design limit. the numbers above hint that the limit might be 64 which smells like the kind of number that might be such a limit well some ports are used implicitly e.g. the screen/compositor uses 1 then it gets 63 mroe of them (port 0, 1, 2, ... 62) then the 65'th fails.

Support for elogind has been upstreamed for a while now

Ho Ho Ho! This issue was fixed by Santa!

"Don't composite fullscreen windows" has no use if you have multiple monitors, and this is an X-specific issue.

So what's going on with this?

this smells here like a video driver issue - like there are a limited number of "contexts" (video ports) for output rendering and once you hit the limit things fail. that's what it smells like at any rate... so either a hardware or driver design limit. the numbers above hint that the limit might be 64 which smells like the kind of number that might be such a limit well some ports are used implicitly e.g. the screen/compositor uses 1 then it gets 63 mroe of them (port 0, 1, 2, ... 62) then the 65'th fails.

i think this is related to my tasks T3441 and T3590 which both have to do with .desktop file parsing, caching and closing of a window or menu.

yes

EDIT: I tried to unplug one of my monitors. With only one monitor issue seems to disappear.