Re: Possible regression (full crash of X)

"Matthew D. Fuller" <[email protected]>
Newsgroups gmane.comp.window-managers.ctwm
Message-ID <[email protected]>
On Mon, May 29, 2017 at 03:05:16AM +0000 I heard the voice of
Yumekui Neru, and lo! it spake thus:
>
> I have been experiencing crashes (relatively) recently, and after
> quite some trial and error, my ctwm install appears to at the very
> least be part in it

Alright, well...

> ctwm: /var/tmp/portage/x11-wm/ctwm-9999/work/ctwm-9999/otp.c:249:
> OtpCheckConsistencyVS: Assertion `PRI(owl) >= priority' failed.

That's the internal consistency checking in the OTP code blowing up
because things aren't in the order we expect them in.  Which means
that something in

>   Land some fixups of OTP and EWMH interaction.
>   e5ea26e47445acb24f153b3d422209e809babce0

is indeed the likely cause.  So some code elves obviously snuck in and
changed something before I landed that branch (the alternative being
that I screwed something up, which is patently ridiculous).

Assertion failure would mean ctwm aborting, which would mean X exiting
if ctwm were the last thing running out of .xinitrc or whatever
(common config).  So from the X perspective, it's not really a
"crash", just ctwm exiting.


> (the window attempts to fill the screen, and pretty much immediately
> crashes to the linux terminal I launched ctwm from).

That at least vaguely suggests it may be the EWMH FULLSCREEN stuff
that's immediately triggering it.  Wine sadly sounds like a good
candidate for doing something screwy with its window[s] too   :(.  On
the plus side, that particular set of consistency checks are all
internal, so it doesn't seem like it's necessary something it's doing
with the X server behind our back, which makes things simpler.

I've got apps using FULLSCREEN with fair regularity here, and I've
been running that code since [before] it landed on trunk without
issue, so there's something at least a _little_ subtle going on.  I
did manage to trip an assertion once in mid-dev, but I'm pretty sure
that was when I was halfway through some changed and I never
reproduced it.  Are you using any OnTopPriority or AlwaysOnTop config
entries, or any of the f.setpriority/etc functions?



-- 
Matthew Fuller     (MF4839)   |  [email protected]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.