The cause of broken Windows GUI builds (when the EXE does not start and does not even produce any error messages) appears to be this usage of GPointer.blit.
There are two noteworthy things about this, though. First, this code has been there since 2005 and never caused any problems. The problems only appeared with binutils > 2.37 (which is why binutils were pinned to 2.37 in the CI script for almost a year). Second, not all machines are apparently equally impacted. On some machines, or under some conditions, the EXE would start normally.
Just for the record, referencing issues: #738, #744
The cause of broken Windows GUI builds (when the EXE does not start and does not even produce any error messages) appears to be this usage of
GPointer.blit.There are two noteworthy things about this, though. First, this code has been there since 2005 and never caused any problems. The problems only appeared with binutils > 2.37 (which is why binutils were pinned to 2.37 in the CI script for almost a year). Second, not all machines are apparently equally impacted. On some machines, or under some conditions, the EXE would start normally.
Just for the record, referencing issues: #738, #744