MazJohn [Mr Arcade] Posted May 27, 2019 Share Posted May 27, 2019 (edited) Since anything beyond Beta 16 up to current release of 9.8, I have been receiving intermittent crashing when exiting games from Big Box.... I get sent back to the windows desktop with a crash report on game exit. It happens using hotkey button to exit and it occurs randomly from any emulator and any theme. My Windows 10 Launch box system has been running stable for the past 4 years until updating past beta 16.... If I go back to Beta 16 prior to the current release the crashing stops. I've tried re-installing Nvidia graphics driver, changing themes, and re-installing Launch box multiple times but issue still continues. I opened a ticket for this but it was suggested I post here instead for help.. I do Appreciate any help possible from the community to resolve, I'm not sure what else to try at this point. Below is the error received. Thanks, Cannot set Visibility to Visible or call Show, ShowDialog, Close, or WindowInteropHelper.EnsureHandle while a Window is closing. App: Big Box Version: 9.8 Type: System.InvalidOperationException Site: Void VerifyNotClosing() Source: PresentationFramework at System.Windows.Window.VerifyNotClosing() at System.Windows.Window.InternalClose(Boolean shutdown, Boolean ignoreCancel) at System.Windows.Application.DoShutdown() at System.Windows.Application.ShutdownImpl() at System.Windows.Application.ShutdownCallback(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 8:39:13 PM Music.Kill Finished 8:39:15 PM Music.StopAndResumeBackground Start 8:39:15 PM Music.StopAndResumeBackground Start 8:39:18 PM Music.StopAndResumeBackground Start 8:39:18 PM Music.Kill Start 8:39:18 PM Music.Kill Finished 8:39:20 PM Music.StopAndResumeBackground Start 8:39:20 PM Music.StopAndResumeBackground Start 8:39:23 PM Music.StopAndResumeBackground Start 8:39:23 PM Music.Kill Start 8:39:23 PM Music.Kill Finished 8:39:24 PM Music.StopAndResumeBackground Start 8:39:24 PM Music.StopAndResumeBackground Start 8:39:26 PM Music.StopAndResumeBackground Start 8:39:26 PM Music.Kill Start 8:39:26 PM Music.Kill Finished 8:39:27 PM Music.StopAndResumeBackground Start 8:39:27 PM Music.StopAndResumeBackground Start 8:39:28 PM Music.StopAndResumeBackground Start 8:39:28 PM Music.Kill Start 8:39:28 PM Music.Kill Finished 8:39:29 PM Music.StopAndResumeBackground Start 8:39:29 PM Music.StopAndResumeBackground Start 8:39:33 PM Music.StopAndResumeBackground Start 8:39:33 PM Music.StopAndResumeBackground Start 8:39:37 PM Music.StopAndResumeBackground Start 8:39:37 PM Music.Kill Start 8:39:37 PM Music.Kill Finished 8:39:38 PM Music.StopAndResumeBackground Start 8:39:38 PM Music.StopAndResumeBackground Start 8:39:42 PM Music.StopAndResumeBackground Start 8:39:42 PM Music.StopAndResumeBackground Start 8:39:46 PM Music.StopAndResumeBackground Start 8:39:46 PM Music.Kill Start 8:39:46 PM Music.Kill Finished 8:39:48 PM Music.StopAndResumeBackground Start 8:39:48 PM Music.Kill Start 8:39:48 PM Music.Kill Finished 8:39:57 PM Music.Kill Start 8:39:57 PM Music.Kill Finished 8:40:17 PM Music.Kill Start 8:40:17 PM Music.Kill Finished 8:40:18 PM Music.Kill Start 8:40:18 PM Music.Kill Finished 8:40:21 PM Music.StopAndResumeBackground Start 8:40:21 PM Music.Kill Start 8:40:21 PM Music.Kill Finished 8:40:22 PM Music.StopAndResumeBackground Start 8:40:22 PM Music.StopAndResumeBackground Start 8:40:24 PM Music.StopAndResumeBackground Start 8:40:24 PM Music.Kill Start 8:40:24 PM Music.Kill Finished 8:40:29 PM Music.StopAndResumeBackground Start 8:40:29 PM Music.Kill Start 8:40:29 PM Music.Kill Finished 8:40:30 PM Music.StopAndResumeBackground Start 8:40:30 PM Music.StopAndResumeBackground Start 8:40:32 PM Music.StopAndResumeBackground Start 8:40:32 PM Music.Kill Start 8:40:32 PM Music.Kill Finished 8:40:33 PM Music.StopAndResumeBackground Start 8:40:33 PM Music.StopAndResumeBackground Start 8:40:36 PM Music.Pause Start 8:40:36 PM Music.Pause Start 8:40:37 PM Music.Pause Start 8:52:50 PM Music.Resume Start 8:52:52 PM Music.Pause Start 8:52:52 PM Music.Pause Start 8:52:53 PM Music.Pause Start 8:54:43 PM Music.Pause Start 8:54:43 PM Music.Kill Start 8:54:43 PM Music.Kill Finished 8:54:47 PM Exception Edited May 27, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
DOS76 Posted May 27, 2019 Share Posted May 27, 2019 Hopefully that error message means something to @Jason Carrand he can offer some insight. Quote Link to comment Share on other sites More sharing options...
neil9000 Posted May 27, 2019 Share Posted May 27, 2019 10 minutes ago, DOS76 said: Hopefully that error message means something to @Jason Carrand he can offer some insight. Yeah, i was gonna link this in the mod discord. It references "Source: Presentation Framework" so i wonder if its .NET related, have you checked you are up to date there? Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted May 27, 2019 Author Share Posted May 27, 2019 (edited) I have updated .NET to latest version which was version 4.8 .... same crash error on game exits... the crash occurs about once out of evey 5 game exits from BigBox... hope someone here in the community has some ideas or can ping Jason for some feedback... thank you all.... If it helps to know, I am running on latest mainstream windows 10 build , which is version1809 with modern intel platform hardware ... I7 cpu, Nvidia gpu...ddr4 -16gb ram. latest crash after .NET 4.8 update is posted below.... Cannot set Visibility to Visible or call Show, ShowDialog, Close, or WindowInteropHelper.EnsureHandle while a Window is closing. App: Big Box Version: 9.8 Type: System.InvalidOperationException Site: Void VerifyNotClosing() Source: PresentationFramework at System.Windows.Window.VerifyNotClosing() at System.Windows.Window.InternalClose(Boolean shutdown, Boolean ignoreCancel) at System.Windows.Application.DoShutdown() at System.Windows.Application.ShutdownImpl() at System.Windows.Application.ShutdownCallback(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 10:06:11 AM Music.Resume Start 10:06:11 AM Music.Pause Start 10:06:11 AM Music.Resume Start 10:06:13 AM Music.StopAndResumeBackground Start 10:06:15 AM Music.StopAndResumeBackground Start 10:06:15 AM Music.StopAndResumeBackground Start 10:06:16 AM Music.Initialize Start 10:06:16 AM Music.Kill Start 10:06:16 AM Music.Kill Finished 10:06:39 AM Music.StopAndResumeBackground Start 10:06:39 AM Music.StopAndResumeBackground Start 10:06:43 AM Music.StopAndResumeBackground Start 10:06:43 AM Music.StopAndResumeBackground Start 10:06:44 AM Music.StopAndResumeBackground Start 10:06:44 AM Music.StopAndResumeBackground Start 10:06:46 AM Music.StopAndResumeBackground Start 10:06:46 AM Music.StopAndResumeBackground Start 10:06:50 AM Music.StopAndResumeBackground Start 10:06:50 AM Music.Kill Start 10:06:50 AM Music.Kill Finished 10:06:50 AM Music.StopAndResumeBackground Start 10:06:50 AM Music.StopAndResumeBackground Start 10:06:54 AM Music.Pause Start 10:06:54 AM Music.Pause Start 10:06:54 AM Music.Pause Start 10:07:22 AM Music.Pause Start 10:07:22 AM Music.Kill Start 10:07:22 AM Music.Kill Finished 10:07:25 AM Exception Edited May 28, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted May 27, 2019 Share Posted May 27, 2019 @MazJohn [Mr Arcade] Thanks for posting here. I do have a few questions for you: Have you tried disabling pause screens to see if it fixes the issue? Have you tried disabling startup screens to see if it fixes the issue? What hotkey are you using to exit? Are you using anything other than LaunchBox/Big Box to make it work? Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted May 27, 2019 Author Share Posted May 27, 2019 (edited) On 5/27/2019 at 12:16 PM, Jason Carr said: @MazJohn [Mr Arcade] Thanks for posting here. I do have a few questions for you: Have you tried disabling pause screens to see if it fixes the issue? Have you tried disabling startup screens to see if it fixes the issue? What hotkey are you using to exit? Are you using anything other than LaunchBox/Big Box to make it work? Thanks Jason for taking the time to take a look into this... please see my answers to your questions below... 1- disabling pause screen alone from Big-Box options menu did not help ... same crash behavior occurred on BB exit. 2- *Disabling startup screen from Big-Box options menu seems to have prevented the crashing... (unchecked) Note: I have always used startup screens in the past without issue, so i do find this interesting. Again just to mention that this crash on exit issue seems to have begun just after Beta 16 and still occurs for me in the 9.8 final.... by the way, I am using "big logo" theme for startup screens... So in summary, with both pause screen and startup screen disabled the crashing seems to have stopped. 3- its actually controller automation enabled from the options menu which i am using to exit games launched from inside Big-Box. I am using Using Xbox one controllers with buttons 5 (as hold button) &6 used to exit active game (shoulder buttons)... nothing else used otherwise to make it work. In light of the above feedback, i appreciate your thoughts Edited May 29, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted May 30, 2019 Author Share Posted May 30, 2019 (edited) Hope the above info helps. Wondering if this is a system specific issue on my part or something else requiring more time... either way- Any updates? thank you... Edited May 30, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted May 30, 2019 Share Posted May 30, 2019 It is somehow system specific, but it may be hard to figure out how, unfortunately. It's good to know that it's being caused by the startup screens though. Most likely, there's a driver glitch somewhere (maybe video drivers?) that is causing it. Can you look to see if there are any upgrades available for your video drivers? Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted May 30, 2019 Share Posted May 30, 2019 Looking deeper, that error message looks to be a symptom and not the culprit. It's trying to exit LaunchBox\Big Box while the game shuts down, which probably means that there was a previous crash caused by the startup screens, which I still think is likely related to video drivers (we've seen similar things several times before). However, it may help to enable logging in the LaunchBox settings and provide me with the log. Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted May 30, 2019 Author Share Posted May 30, 2019 Jason, Attached is a debug log as requested. I collected it just after a crash. see the very bottom of the log. not sure what it means but it seems to be related to a shutdown.... by the way, I updated my GTX1060 Nvidia driver to latest release available dated 5/27/19, enabled debugging in launchbox options, the played some games and it crashed on exit within a few tries. Log immediately attached after the crash.... maybe this will help you if not me but it was worth a shot.... I have a backup of my Launchbox install. would there be any specific files that i could replace from my backup that are related to the shutdown issue? thanks anyways for taking your time ... i will have to do some testing on my build until i can isolate, or just keep startup screens disabled for now. regards, Debug 2019-05-30 05-02-01 PM.log Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted May 30, 2019 Share Posted May 30, 2019 Okay, the strange thing about that log is that Big Box seems to be running through its exit process when the game is ending, which unless that's what you're telling it to do, isn't right. I think the errors are coming from the fact that Big Box is exiting while the game is exiting at the same time. Just a shot in the dark, what key do you have bound to Exit in Big Box? I wonder if that's the issue. Quote Link to comment Share on other sites More sharing options...
JoeViking245 Posted May 30, 2019 Share Posted May 30, 2019 Could it be getting a 'double-click' effect? Like hitting Esc to exit the game then Esc again that exits BB? Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted May 31, 2019 Author Share Posted May 31, 2019 (edited) 19 hours ago, Jason Carr said: Just a shot in the dark, what key do you have bound to Exit in Big Box? I wonder if that's the issue. Under controller buttons in BigBox, the exit button is set to none. Also worth noting; 1- I did have "use all controllers" enabled under controller automation , so i tried unchecking that but to be honest I never had a problem before in leaving that checked. 2- Under keyboard mappings, i un-assigned the default "x" button from the exit command just for the hell of it.... 3- Under keyboard automation, I unchecked "use keyboard automation" .... this is a new feature unless mistaken... wonder if that being enabled was causing any issues... this being said, I never changed any of the default keys while it was enabled. I just disabled it now so I will see if that helps in any way. Also, please note that the problem is intermittant (estimate 1 out of every 5 exits results in crash) - what I am getting at, is that this "double exit" crash (if i may call it that) is not consistant.... What i do find a little confusing is that under "controller buttons" and "controller automation" , the same joypad keys are permitted to be used in both sections... I'm throwing a needle at a hair here, but could there be some sort of conflict that causes it to crash from that? I removed all Joypad assignments from controller buttons anyways just to help further isolate... lol... To add more to my own punishment (just being sarcastically funny here) ... I removed all emulator entries for "auto hotkey script" inside launch-box itself. Another note; I've been updating launchbox since version 5 from each beta to the next over time ... never had any issues until now... been loving it. Thanks... Edited May 31, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted June 3, 2019 Share Posted June 3, 2019 Alright, I'm still fairly lost here, I will admit. Unfortunately this situation somehow seems to be a one-off; I haven't had any other reports of similar issues, so figuring this one out is going to be difficult. On 5/31/2019 at 10:04 AM, MazJohn [Mr Arcade] said: Under controller buttons in BigBox, the exit button is set to none. That pretty much throws my previous suspicions out of the water. On 5/31/2019 at 10:04 AM, MazJohn [Mr Arcade] said: 1- I did have "use all controllers" enabled under controller automation , so i tried unchecking that but to be honest I never had a problem before in leaving that checked. It shouldn't really be related to this at all. I guess you never know though. On 5/31/2019 at 10:04 AM, MazJohn [Mr Arcade] said: What i do find a little confusing is that under "controller buttons" and "controller automation" , the same joypad keys are permitted to be used in both sections... I'm throwing a needle at a hair here, but could there be some sort of conflict that causes it to crash from that? I removed all Joypad assignments from controller buttons anyways just to help further isolate... lol... They're used in different scenarios, and it is assumed that if you set one up that you won't use the same buttons for the other. I suppose it could be related if you had bound them to the same buttons, but otherwise, I doubt that it has anything to do with the issue. What emulators are you using that you've noticed the issue with? Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted June 5, 2019 Share Posted June 5, 2019 @MazJohn [Mr Arcade] Been waiting to put out the official 9.9 release, hoping we can figure this out and get it fixed. If you're around, let me know what emulators you're seeing this problem with. Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted June 5, 2019 Author Share Posted June 5, 2019 (edited) Jason, Sorry for not being able to respond back sooner... The crash to desktop problem seems to be happening on all emulators... I can say for a fact, it happens on Retro-arch which covers a great deal of systems for me personally, but it also occurred on pcsx2 and Dolphin. I have seen it more on Retro-arch simply because more systems are using it..... Something important to say.... I mentioned it way back in my original post- When I revert back to Beta -16 the issue seems to stop occurring ... anything past beta 16 all the way up to current 9.8 release causes me to have this issue.... 9.8 was crashing almost every time on emulator exits the past few days... by the way, In my last post above from past Friday, none of those other things mentioned that i could try seemed to help.... *Disabling startup screen from Big-Box options menu seems to have prevented the crashing in 9.8 final... (unchecked) I stress tested my My CPU and memory running on z390 platform and the Windows 10 system is stable. No other applications are experiencing issues- its a dedicated Launchbox build, and alsways has been... Much do Appreciate you looking into this for the next release and taking some of your your Dev time to help. Regards, Edited June 5, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted June 5, 2019 Share Posted June 5, 2019 Alright, I looked into this a little deeper. For beta 16, we added support for custom exit AutoHotkey scripts, so my best guess is that it's somehow related to that. Let's just test with Retroarch, since I do a lot of testing with it myself and I know it works on all my machines. If you edit the Retroarch emulator in LaunchBox, what do you have in the Exit AutoHotkey Script tab? Does it match mine? If so, try emptying it and adding a single line like this: Sleep 50 That will basically do nothing, but force it not to execute the default AutoHotkey script, so that should at least let us know if we're on the right track as to the problem. Thanks. Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted June 6, 2019 Author Share Posted June 6, 2019 (edited) updated back to 9.8 official then checked retroarch autohotkey exit as requested. reads as follows; ; No custom exit script is necessary for Retroarch ; since it already uses the Escape key by default This setting was never touched. my launchbox backup copy was also set the same way for retroarch. edit.. opps.. will change to sleep 50 as requested and report back... Edited June 6, 2019 by MazJohn [Mr Arcade] Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted June 6, 2019 Share Posted June 6, 2019 2 minutes ago, MazJohn [Mr Arcade] said: updated back to 9.8 official then checked retroarch autohotkey exit as requested. reads as follows; ; No custom exit script is necessary for Retroarch ; since it already uses the Escape key by default This setting was never touched. my launchbox backup copy was also set the same way for retroarch. Okay, good to know. Can you try putting that script in that I suggested? Quote Link to comment Share on other sites More sharing options...
MazJohn [Mr Arcade] Posted June 6, 2019 Author Share Posted June 6, 2019 (edited) 27 minutes ago, Jason Carr said: Okay, good to know. Can you try putting that script in that I suggested? Jason, OK, so when i changed the default script in retroarch to "sleep 50" and re-started big-box, I can now no longer exit a game using the defined "hold button" and "close active window" using my Xbox one controller.... I assume this is to be expected behavior since the default script is no longer running...... ? I then reset to use the default retroarch script again, and within 3 game exits, it crashed again on the third try. This time it didnt even come back with an error dump at all... it just exited Launchbox completely and I am returned immediately to the windows desktop. (running 9.8 official) Thank you.... Edited June 6, 2019 by MazJohn [Mr Arcade] fixed typos Quote Link to comment Share on other sites More sharing options...
![MazJohn [Mr Arcade]](https://forums.launchbox-app.com/uploads/monthly_2017_07/hqdefault.thumb.jpg.507e7dd1a14a60db4e5aeb6396622e1a.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.