Page 1 of 1
Windows 10 can't handle big windows...?
Posted: 10 Oct 2016, 06:04
by lexikos
On my Windows 10 (version 1607) system, this code
crashes the desktop window manager,
kills my entire login session and kicks me back to the login screen:
At first I thought it was a driver problem, because after I logged back in Windows told me the driver failed to start. However, re-running the code while the video driver is disabled gives the same result.
Does anyone else have this problem? (I'd suggest closing any programs before testing...)
It does not cause any problem on my Windows 7 VM.
Re: Windows 10 can't handle big windows...?
Posted: 10 Oct 2016, 06:29
by jNizM
dbgview.exe
As user with
Capture Win32
Code: Select all
# Time Debug Print
00000003 12.21135521 [4216] onecore\base\appmodel\resourcepolicy\gameconfigstore\client\gameconfigstoreclient.cpp(104)\resourcepolicyclient.dll!00007FFB92AB976C: (caller: 00007FFB81DB0AD3) LogHr(5) tid(b38) 80070490 Element nicht gefunden.
00000004 12.61060333 [4216] shell\lock\abovelock\shellcomponent\lockscreenapppositioner.cpp(340)\AboveLockAppHost.dll!00007FFB861E4620: (caller: 00007FFB861E475F) ReturnHr(1) tid(614) 8000FFFF Schwerwiegender Fehler
00000005 12.61063385 [4216] shell\lock\abovelock\shellcomponent\lockscreenapppositioner.cpp(367)\AboveLockAppHost.dll!00007FFB861E477E: (caller: 00007FFB861E321B) ReturnHr(2) tid(614) 8000FFFF Schwerwiegender Fehler
00000006 12.61064720 [4216] shell\lock\abovelock\shellcomponent\lockscreenapppositioner.cpp(256)\AboveLockAppHost.dll!00007FFB861E323A: (caller: 00007FFB957F7DE3) ReturnHr(3) tid(614) 8000FFFF Schwerwiegender Fehler
As admin with
Capture Global Win32
Code: Select all
# Time Debug Print
00000002 9.49877167 [608] onecore\base\appmodel\resourcepolicy\gameconfigstore\server\gameconfigstoreserver.cpp(535)\resourcepolicyserver.dll!00007FFB927265EB: (caller: 00007FFB92729C7B) LogHr(276) tid(700) 80070002 Das System kann die angegebene Datei nicht finden.
00000003 9.49880981 [608] onecore\base\appmodel\resourcepolicy\gameconfigstore\server\gameconfigstoreserver.cpp(1999)\resourcepolicyserver.dll!00007FFB92729C9D: (caller: 00007FFB927292AC) LogHr(277) tid(700) 80070002 Das System kann die angegebene Datei nicht finden.
00000004 9.49884129 [608] onecore\base\appmodel\resourcepolicy\gameconfigstore\server\gameconfigstoreserver.cpp(2147)\resourcepolicyserver.dll!00007FFB9272A246: (caller: 00007FFB927292BD) LogHr(278) tid(700) 80070490 Element nicht gefunden.
00000005 9.49887371 [608] onecore\base\appmodel\resourcepolicy\gameconfigstore\server\gameconfigstorerpcserver.cpp(437)\resourcepolicyserver.dll!00007FFB927245AC: (caller: 00007FFB957F7DE3) LogHr(279) tid(700) 80070490 Element nicht gefunden.
00000006 9.49899197 [4648] onecore\base\appmodel\resourcepolicy\gameconfigstore\client\gameconfigstoreclient.cpp(104)\resourcepolicyclient.dll!00007FFB92AB976C: (caller: 00007FFB80460AD3) LogHr(6) tid(1574) 80070490 Element nicht gefunden.
00000007 9.62916374 [828] onecore\base\flighting\flightsettings\broker\lib\flightsettingsapicommon.cpp(626)\flightsettings.dll!00007FFB8893E24B: (caller: 00007FFB8893AB7F) ReturnHr(1) tid(13f4) 80070002 Das System kann die angegebene Datei nicht finden.
00000008 9.91540909 [608]
00000009 9.91540909 [608] Session 7 is terminating after waiting for 0 ms; but process `winlogon.exe' (id=4296) is still alive.
00000010 9.91540909 [608] Please contact the owner of `winlogon.exe' to investigate the cause
00000011 9.91543388 [608] Attempting to terminate the process.
00000012 9.91709614 [608]
00000013 9.91709614 [608] Session 7 is terminating after waiting for 0 ms; but process `sihost.exe' (id=1092) is still alive.
00000014 9.91709614 [608] Please contact the owner of `sihost.exe' to investigate the cause
00000015 9.91715527 [608] Attempting to terminate the process.
00000016 9.96126842 [4648] shell\lock\abovelock\shellcomponent\lockscreenapppositioner.cpp(340)\AboveLockAppHost.dll!00007FFB8B004620: (caller: 00007FFB8B00475F) ReturnHr(1) tid(7d0) 8000FFFF Schwerwiegender Fehler
00000017 9.96129990 [4648] shell\lock\abovelock\shellcomponent\lockscreenapppositioner.cpp(367)\AboveLockAppHost.dll!00007FFB8B00477E: (caller: 00007FFB8B00321B) ReturnHr(2) tid(7d0) 8000FFFF Schwerwiegender Fehler
00000018 9.96131325 [4648] shell\lock\abovelock\shellcomponent\lockscreenapppositioner.cpp(256)\AboveLockAppHost.dll!00007FFB8B00323A: (caller: 00007FFB957F7DE3) ReturnHr(3) tid(7d0) 8000FFFF Schwerwiegender Fehler
Re: Windows 10 can't handle big windows...?
Posted: 10 Oct 2016, 06:57
by lexikos
I'm not sure how any of that is relevant. I don't think it's indicative of anything other than what I already knew because it was blatantly obvious: the session was terminated. (Assuming it crashed for you too, and that was the debug output.)
Session 7 is terminating after waiting for 0 ms;
Was it a long wait?
Re: Windows 10 can't handle big windows...?
Posted: 10 Oct 2016, 07:13
by jNizM
lexikos wrote:Was it a long wait?
Nope
Double click -> black screen -> wait 5 sec's -> relog
Tested on Win10 Ent Version 1607 (Build 14393.51)
Crashes also with 32766.. others not tested
Re: Windows 10 can't handle big windows...?
Posted: 10 Oct 2016, 21:42
by lexikos
I was referring to the 0ms wait.
Re: Windows 10 can't handle big windows...?
Posted: 11 Oct 2016, 02:48
by just me
I'm still on Win 10 Pro x64 build 10240 here (because later versions refuse to run on my machine). The scripts doesn't crash, but the window isn't visible. The window switcher shows some odd-looking AHK GUI preview, but cannot bring it up visibly. It's capturing mouse and keyboard input, though.
Re: Windows 10 can't handle big windows...?
Posted: 11 Oct 2016, 09:12
by joedf
Very weird... I'm currently running a full scan so I won't be testing this anytime soon. However, does it crash when you grow the window gradually?
Re: Windows 10 can't handle big windows...?
Posted: 14 Oct 2016, 12:34
by Elesar
Windows 10 Pro v1607 here. Confirmed that this crashes my system as well. I don't get kicked to login screen, but it does crash my drivers and kicks me down to a single monitor. I don't have any issue with windows at my total resolution, or even a few hundred pixels over my total res.
Currently running 6 1920x1080 monitors in a 3x2 layout for a res of 5760x2160. Tested up to 6000x3000 without issue so far.
Re: Windows 10 can't handle big windows...?
Posted: 15 Oct 2016, 00:41
by joedf
So, Ive tested it. It freeze/slows my explorer.exe ie taskbar, desktop, etc. However, I was able to run task manager to kill the script.
Definitely something weird going on. I have a feeling Win10 has lots of problem with their new "explorer.exe". My login screen would occasionally freeze.
Could be unrelated. Either way, it's weird stuff.
Re: Windows 10 can't handle big windows...?
Posted: 16 Oct 2016, 00:35
by Helgef
How big windows are expected to work?
Re: Windows 10 can't handle big windows...?
Posted: 16 Oct 2016, 03:25
by lexikos
It's not about whether the window works, just how badly the system handles it.
I don't want to make big windows; I only encountered this problem because a combination of AutoHotkey bugs (most of which were fixed in v1.1.24.02) caused the window to be resized to (up to) 32768 x 32768 under specific conditions (which likely never happen in the real world). I was totally confused when I ran a simple Gui test script (which did not use any hard-coded coordinates) and got kicked back to the login screen.
The number comes from the minimum coordinates possible for a window, which seem to be -32768,-32768.
Re: Windows 10 can't handle big windows...?
Posted: 16 Oct 2016, 07:03
by Helgef
lexikos wrote:
[...]
I was totally confused when I ran a simple Gui test script (which did not use any hard-coded coordinates) and got kicked back to the login screen.
[...]
I see.
As you said,
Gui, Show, w32767 h32767 doesn't seem to make trouble on win7. For me, the window just doesn't show. However, if I half the width and height, the window actually shows, and then I get problems, aero theme gets disabled, which I guess is related to dwm. No login screen though.
Good luck
Edit: English.
Re: Windows 10 can't handle big windows...?
Posted: 16 Oct 2016, 16:05
by lexikos
For you on Windows 7?
When I say it doesn't cause any problems on my Windows 7 VM, I mean it doesn't cause any problems on my Windows 7 VM. The window shows, it is the size requested, and Aero continues working.
Re: Windows 10 can't handle big windows...?
Posted: 16 Oct 2016, 23:44
by Helgef
lexikos wrote:For you on Windows 7?
Yes, Aero theme got turned off, it happened twice, and I rebooted after the first time, because my computer had been on for several week. However, I don't think I have updated ahk on that computer, I'll have to check what version I have.
Re: Windows 10 can't handle big windows...?
Posted: 17 Oct 2016, 02:15
by Helgef
On win7, ahk 1.1.24.02 64bit unicode, running this code:
consistently gives me a traytip, saying that the "color scheme has changed to windows 7 basic" (translated from my lang.), and aero theme gets disabled. The gui shows. No other issues.
If I add
above the
Gui, show, the theme doesn't change, no traytip.
Re: Windows 10 can't handle big windows...?
Posted: 23 Nov 2016, 13:32
by Drugwash
Just for fun I tested this "anomaly" on my 98SE under AHK Basic.
With size set to max 32742x32742 the window shows, everything else works perfectly.
With sizes larger than that up to 32767x32767 the window briefly shows (if at all) then dissapears and there's only the taskbar button advertising its presence. Everything else works correctly.
In either case there's only an ~2MB memory drop (size of AHK exe).
Told ya 9x rocks!
Just kidding. But the test is real and accurate nonetheless.
(fixed minor typo)
Re: Windows 10 can't handle big windows...?
Posted: 05 Dec 2016, 04:09
by simplysunny
Really? I haven't even upgraded to Windows 10 yet... (still 7), but this is a little worrying.
Re: Windows 10 can't handle big windows...?
Posted: 22 Dec 2017, 23:02
by lmstearn
Very interesting. Here on 1709 (AMD) everything freezes - CTR-Alt-Del to escape. Once Task Mgr is invoked, it's as if nothing happened. Absolutely nothing in the logs.