> 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.
I see, that makes sense.
> > (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?
I have no idea what it would imply in the context of window-managers, but the
graphical mode that I used was "borderless" rather than fullscreen, so maybe
filling the screen might not have been the best words to use.
It did not initially occur to me to test my configuration options, though
I believe I have narrowed it down to one specific option now (StartIconified),
and was able to reproduce the issue with the configuration below:
#.twmrc:
Function "move-or-lower" { f.move f.deltastop f.lower }
Function "move-or-raise" { f.move f.deltastop f.raise }
Function "move-or-iconify" { f.move f.deltastop f.iconify }
Button1 = : root : f.menu "defops"
Button1 = m4 : window|icon|title : f.function "move-or-raise"
Button2 = m4 : window|icon|title : f.resize
Button3 = m4 : window|icon|title : f.function "move-or-lower"
"F8" = : all : f.iconify
"F3" = shift mod1 : all : f.restart
"F3" = shift : all : f.identify
menu "defops"
{
"terminal" !"xfce4-terminal &"
"xterm" !"xterm &"
"exit" f.quit
}
StartIconified { "League of Legends.exe" }
#EOF
Commenting out the iconified-line, I was able to do 10 successful launches
in a row without reproducing the issue (out of the 10 I tried). When I added
the line back, it happened on the first attempt (on commit e5ea26e).
Might this be related to the StartIconified-thread from a while ago (earlier
this year I believe) ? From what I remember, the debug entries I used then
logged that the window attempted to start iconified, rather than "not",
although the window started raised (perhaps by raising itself a moment after
starting iconified).
