![]() While this article is largely about third-party screenshot tools, we really should mention all the screenshot tools built into Windows itself. Have window with class Windows.UI.Core.The Best Tool You Already Have: Windows Itself.So the most probable conditions to replicate SOE is: Killing ShellExperienceHost.exe fixed the issue. The owner process was ShellExperienceHost.exe. It looks like this was the only window on my system that falls into IsApp case (window class was Windows.UI.Core.CoreWindow). I took the window handle from the stack trace shown above and check process id of the owner. State of WindowDetails when the crash occured: It seams that this problem - when it occurs - is pretty persistnent for a specific set of time and than suddenly it fix itself.ĭwmApi.IsDwmEnabled is false for most cases or gotFrameBounds is false or IsApp is false(?) ![]() Maybe outer ifs break the call chain in most cases. I cannot understand why it is so hard to reproduce. I have no time at the moment to fully understand and debug this piece of code. WindowRectangle getter calls Maximised getter Visible getter calls WidowRectangle getter WindowDetails.cs:666 (yes, its actually line 666 :) )Ĭall chain stars in WindowDetails.cs:1555 code checks if window is visible. Machine is company-managed (so sorry for the multitude of. 08:47:30,765 INFO - Starting background task to check for updates 08:47:10,545 INFO - Loading language file C:\Program Files\Greenshot\Languages\Plugins\ExternalCommand\language_externalcommand-de-DE.xml 08:47:10,545 INFO - Loading language file C:\Program Files\Greenshot\Languages\language-de-DE.xml 08:47:10,545 INFO - Loading language file C:\Program Files\Greenshot\Languages\Plugins\ExternalCommand\language_externalcommand-en-US.xml 08:47:10,545 INFO - Loading language file C:\Program Files\Greenshot\Languages\language-en-US.xml 08:47:10,543 INFO - Searching language directory 'C:\Program Files\Greenshot\Languages' for help files with pattern 'help-*.html' 08:47:10,542 INFO - Retrieving language details from file: C:\Program Files\Greenshot\Languages\Plugins\ExternalCommand\language_externalcommand-sr-RS.xml 08:47:10,541 INFO - Retrieving language details from file: C:\Program Files\Greenshot\Languages\Plugins\ExternalCommand\language_externalcommand-kab-DZ.xml 08:47:10,539 INFO - Searching language directory 'C:\Program Files\Greenshot\Languages' for language files with pattern 'language*.xml' 08:47:10,536 INFO - Not adding non existing language path C:\Users\NAME\AppData\Roaming\Greenshot\Languages\ 08:47:10,536 INFO - Not adding non existing language path C:\Program Files\Greenshot\App\Greenshot\Languages 08:47:10,394 INFO - Can't find file: C:\Users\NAME\AppData\Roaming\Greenshot\Greenshot-fixed.ini 08:47:10,394 INFO - Using ini file C:\Users\NAME\AppData\Roaming\Greenshot\Greenshot-fixed.ini 08:47:10,393 INFO - Loading ini-file: C:\Users\NAME\AppData\Roaming\Greenshot\Greenshot.ini 08:47:10,393 INFO - Using ini file C:\Users\NAME\AppData\Roaming\Greenshot\Greenshot.ini 08:47:10,391 INFO - Loading ini-file: C:\Program Files\Greenshot\Greenshot-defaults.ini 08:47:10,389 INFO - Using ini file C:\Program Files\Greenshot\Greenshot-defaults.ini 08:47:10,389 INFO - Checking for portable mode. 08:47:10,358 INFO - Using ProductName Greenshot Logfile isn't too interesting, pasting the excerpt here: After crashing and closing itself, I can re-start it and access the "about" dialogue, but hitting the "print" key or Alt-Print or clicking "Bereich abfotografieren" in the systray closes the application again. I can confirm the exactly same behaviour on Win 10 21H2 with 1.3.256 64bit. Greenshot simply closed and I had to open it again (it happened over and over again), whenever I triggered the printscreen button ![]()
0 Comments
Leave a Reply. |