Galaxian Posted Monday at 04:09 PM Posted Monday at 04:09 PM Please help. Many thanks. Object reference not set to an instance of an object. App: Big Box Version: 13.21 Theme: Default Type: System.NullReferenceException Site: Boolean CompareMetaWatcher(System.Object, System.Object, Boolean) Source: Unbroken.LaunchBox.Windows at Unbroken.LaunchBox.Windows.Integrations.MAME.MameHighScores.CompareMetaWatcher(Object reference, Object token, Boolean extractres) at InfoPrototypeWatcher.FindDataSchema(String reference, String token, Boolean extractres, InfoPrototypeWatcher) at Unbroken.LaunchBox.Windows.Integrations.MAME.MameHighScores.<>c__DisplayClass20_0.AwakeMetaManager(Object sender, EventArgs args) at System.Diagnostics.Process.RaiseOnExited() at System.Diagnostics.Process.CompletionCallback(Object waitHandleContext, Boolean wasSignaled) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.RegisteredWaitHandle.PerformCallback(Boolean timedOut) at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Recent Log: 17:03:51 Exception Quote
C-Beats Posted Tuesday at 11:46 AM Posted Tuesday at 11:46 AM What game were you on when you saw this error? Quote
Galaxian Posted Tuesday at 02:59 PM Author Posted Tuesday at 02:59 PM (edited) It might have been Grid Seeker, but don’t quote me on that. Certainly the issue isn’t confined to a single game. I only noticed the error when I’d exited the game. Edited Tuesday at 03:00 PM by Galaxian Quote
TigerT82 Posted Thursday at 07:00 PM Posted Thursday at 07:00 PM Experiencing similar errors when exiting games... not any one in particular. Also, if left running, there seems to be a memory leak somewhere. Getting out of memory errors and have to close LaunchBox. These issues only started after 13.21 update. Quote
C-Beats Posted Thursday at 08:01 PM Posted Thursday at 08:01 PM 59 minutes ago, TigerT82 said: Experiencing similar errors when exiting games... not any one in particular. Also, if left running, there seems to be a memory leak somewhere. Getting out of memory errors and have to close LaunchBox. These issues only started after 13.21 update. There is a known issue with hibernate and some modes of sleep causing memory errors when returning to the application. If you're seeing that error and NOT entering hibernation OR sleep then file a bug report for it please. Quote
TigerT82 Posted yesterday at 05:05 AM Posted yesterday at 05:05 AM Good to know.... Fairly new to LaunchBox and don't know if I've ever left it on for a long period of time before. I just set up a separate Arcade desk and I've been leaving it turned on much more frequently. Quote
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.