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.