duerra

@AstroBob as a dev myself, Schrödinger's Bugs can be exceptionally frustrating. I'm glad you were able to reproduce it, and your description and hypothesis on the issue does track for me. I hope you guys are able to identify resolution for it. As you noted, I have not found a reliable way to reproduce the issue. It happens seemingly at random. Sometimes I'll get it more than once a day, and other times I could go a week or two without seeing it resurface.

Hello - Here is output from Focus Logger when this issue occurred again for me today. Note that when clicking the already-expanded LaunchBox instance, nothing was recorded in the app. When attempting to click icon on the task bar, you can see the DisplayFusion trigger followed by the "Idle" trigger. Nothing else I have seen produces this "Idle" output. I decided in this situation to try and exit DisplayFusion, but that also did not correct the problem. I also locked and unlocked my computer, which also did not make any difference.

I could try the focus logger app, but I'm very hesitant to start all over again with LaunchBox. I've been curating my LB install for many years now, including many custom platform categories that I've set up, etc. I don't have any real custom AHK scripts outside of basic support for ESC key-to-quit support for a couple emulators. I don't do anything particularly unusual, but it is highly curated and meticulously managed.

@AstroBob I had startup screens disabled for a long time due to eXoDOS not being compatible, but recently re-enabled them for everything else except eXoDOS, in part to try and see if it could be related to this issue somehow. It has persisted with both settings. My shutdown screens are whatever is default. Just converted notifications from LaunchBox notifications -> Windows notifications, since disabling them isn't an option that I can select. I'll report if it happens again following this change. I do not use automatic store imports. This problem existed before that feature was even released. To be clear, I believe the issue arises in other scenarios outside of game launch/shutdown, but am not 100% sure on that. @Sbaby seems confident that it arises independently of game launches.

It just happened again, again the last game played was Rocket League. Here is my task manager output:

Here's my "functional" LaunchBox instance: My "frozen" instance earlier today was identical to this, so I didn't save the screenshot. Note: I just launched a fresh instance, which is why the processor usage is so high.

I actually just checked that independently earlier today after the "freeze" happened again after a round of Rocket League. There are 2 subprocesses, but they were there after LaunchBox restart, too.

Just bumping this to page 2 so a team member doesn't accidentally miss it.

I've anecdotally felt like the same thing, that it happens randomly and not as a result of a game launch or close action, but could not be 100% sure that it didn't happen after closing a game from a previous play session and that I didn't notice until I came back later.

@Sbaby let's do a little recon here to see if we can help out the team. Do you have any software installed which may interact with the Windows environment or task bar in any way, such as my situation with DisplayFusion? Do you have any non-default settings in your LaunchBox install as it pertains to games - for example, I have the Launch Screen disabled in my settings. Other things might include (but not in my case), AHK scripts or other software which may get invoked when launching a game.

Please see the attached video. pFN1V0aIqA.mp4

Hi @AstroBob - yes, I have an NVIDIA 4090 on the latest 566.05 driver version with Windows 10. I update it regularly, so it's not likely version-specific. I do use DisplayFusion, which has functions integral to my workflow (such as a separate task bar for my second [vertical] monitor). I do use full-screen settings typically in games, though this has shown up even for games I play regularly and do not consistently see this issue. It can sometimes happen within minutes of loading LaunchBox, and other times it could be days between issues. It never happened until it did, and since then I have had the problem across all versions of LaunchBox and GPU driver. I also used DisplayFusion and my physical monitor setup prior to this issue starting. I may have upgraded my second monitor to an DisplayPort input from a DVI input in August 2023, which was just after I first reported this issue. The issue began beginning a couple of versions before the original post date. My main monitor is G-SYNC, and my secondary monitor is FreeSync (but the old secondary monitor did not have VRR).

To be clear, I mentioned dual monitors in case it helped in identifying the root cause. I don't necessarily believe dual monitors to be the issue, however. I thought maybe after recovering from idle monitor power down, but that is definitely not the case, either. It doesn't always happen after closing a game, I don't think, though that definitely does happen. It's not the LaunchBox freezes as in the typical app hanging freeze. It's that I can't actually click into LaunchBox and navigate around in anything any longer. You can't even properly select the window from the task bar. If you have it behind another window, for instance, it won't be returned to the foreground when clicking the task bar. You can alt-tab to LaunchBox, but you are still unable to interact with it. The only way to address the issue is to task kill it from the task manager and launch it again. As for the version, it has been happening for well over a year now, across all versions of LaunchBox since before I reported it in July 2023. I update regularly.

Still continue to have this issue. This morning, I've had to task kill LB 3 separate times due to issues with being able to restore interaction capabilities with the LaunchBox app. I really am at a loss as to better helping identify why this is happening. It cannot obviously be reproduced, but it happens to me multiple times a week, if not multiple times a day.

@Lordmonkus can you please move this to the troubleshooting forum?