Anyone got a constant crash bug when clicking around in launchbox?

[Dybdal]

Need to know if this is just my installation thats buggy or if its a common thing, before i bug report it.
Getting this bug every single day.

Object reference not set to an instance of an object.

App:     LaunchBox
Version: 13.20
Theme:   Default
Type:    System.NullReferenceException
Site:    Void RunMultipartPublisher()
Source:  LaunchBox

   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.<>c__DisplayClass620_0.RunMultipartPublisher()
   at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.FlushMultipartTask(Object)
   at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.RemoveStatelessCallback()
   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)

Recent Log:

   23:01:42 Exception

[C-Beats]

13 hours ago, Dybdal said:

Need to know if this is just my installation thats buggy or if its a common thing, before i bug report it.
Getting this bug every single day.

Object reference not set to an instance of an object.

App:     LaunchBox
Version: 13.20
Theme:   Default
Type:    System.NullReferenceException
Site:    Void RunMultipartPublisher()
Source:  LaunchBox

   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.<>c__DisplayClass620_0.RunMultipartPublisher()
   at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.FlushMultipartTask(Object)
   at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.RemoveStatelessCallback()
   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)

Recent Log:

   23:01:42 Exception

Can you confirm what you're doing when you get this error?

[Dybdal]

Favoriting stuff, clicking around on games, anything that causes the database to be read.
Im thinking this is a borked install on my end, if others arn't having it. reason why i decided not to bug report it.

It's all singular actions taken that causes it, so im thinking someone else would have dealt with the same issue is this error was fixable on your end.

Edited March 11 by Dybdal

[C-Beats]

32 minutes ago, Dybdal said:

Favoriting stuff, clicking around on games, anything that causes the database to be read.
Im thinking this is a borked install on my end, if others arn't having it. reason why i decided not to bug report it.

It's all singular actions taken that causes it, so im thinking someone else would have dealt with the same issue is this error was fixable on your end.

Are you pressing favorite in Game Details and then quickly changing games selected? I see the call that stack is pointing to but it look's fairly safe. I do see how it's possible to get that, but from what I briefly saw you'd have to be changing games immediately after pressing the fav button.

[Dybdal]

Sorry for the slight delay in response, obligations got in the way.
Did some short tests and it does indeed seem to be related to favoriting a game, then swapping quickly to the next game.

[kurzih]

Hi,

@C-Beats, @Dybdal

Can confirm the bug is still present with the latest version. I was favoriting some amiibos I already had in my database/collection - easy to reproduce, crashes every time:
 

Object reference not set to an instance of an object.

App:     LaunchBox
Version: 13.21
Theme:   Old Default (Legacy)
Type:    System.NullReferenceException
Site:    System.Object InstantiateCompositeInitializer(System.Object)
Source:  LaunchBox

   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.<>c__DisplayClass622_0.InstantiateCompositeInitializer(Object)
   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.<>c__DisplayClass622_0.ResolveTypePredicate()
   at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.ConcatMetaStrategy()
   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)

Recent Log:

   19.39.13 Exception

 

BigBox has had also issue with speed & favoriting for years, I guess LB/BB doesn't like "Fast-Favoriters", a post of mine from 2018 (already old report by then):

PS. Oh, and before I forget: there's been an old bug in BigBox: Favoriting. I'm using a 360 Controller and I'm using BigBox to view my collection and pick the best I have and favorite them. I don't know if I'm too fast, but sometimes it doesn't put the "favorite" icon when I press it - but it does give the sound as if it would have been pressed. I press again and then it shows the icon, but it actually doesn't save it (going back to the previous menu and back the game list - not favorite after all). Could you check it?
 

But for me, the most annoying and quite "new" bug still present is with Launchbox/Retroarch not loading instantly with certain cores after the integration / file dependency was added:

I hope there will be some solution... A program's launch shouldn't be delayed/freezed by around 5 seconds for no reason.