Crashing on "Populating Local Metadata"

[TheNewClassics]

Hi LB team; I'm getting a pretty consistent crash with the "Populating Local Metadata" step on opening LB. Every 4th or 5th load, it does eventually load properly.

I took a look in the Windows Event Viewer and got a log and a couple readouts. Wondering if anyone could take a look and see if there's anything to go by in there. 

Along the same lines, I consistently get a crash when downloading images/metadata and get to the "Clearing Image Cache" step. From what I can see in the logs, it appears to be a NET core error. I've tried uninstalling/reinstalling all of the NET core packages but the crashes still continue. 

Error log.txt Error summaries compiled.txt Report.wer

[TheNewClassics]

Not sure if this will be helpful for anyone in the future, but I found an old topic in which C-Beats suggested to set "EnableAutomatedImports" to false in the settings.xml file, and now it loads every time without issue.

Unfortunately, I'm still getting crashes related to Net core in other places., at least according to the Event Viewer.

Edited October 23 by TheNewClassics

[AstroBob]

Hey @TheNewClassics

Sorry to hear about the issues here, but thanks for reporting it. May I confirm a few things to try and narrow this down:

- What version of LaunchBox are you currently using? Did you recently upgrade?

- How long have you been able to consistently reproduce this crash, is it something that's only started happening recently, or it's been happening for a while. Did you notice it started with any version update?

- How many games are in your library?

Let us know and we'll see if we can uncover anything

[TheNewClassics]

Thanks for taking a look AstroBob; so as of now, my main issue is crashing at various points in LB due to what looks to be a NET core error. But it is definitely reproductible when downloading metadata/media. To respond to your questions:

- 13.17. I've been upgrading as the betas have come along for several years

- I'd say at least 6 months now, maybe longer. I can't pin down which version did it. I did notice it's a NET core issue according to Windows Event Viewer, so I was looking to see when LB updated it's NET core version

- Around 30k

Thanks again; I've been trying to troubleshoot this for about a week. Was fortunate to find a fix for the initial load issue, but these other crashes have been very tough to pin down.

[TheNewClassics]

Couple more things I've figured out @AstroBob that could potentially be helpful narrowing down the issue.

- I've tried a fresh install of LB 13.17 in a different folder. I still seem to get NET core errors.

- Tried reinstalling/uninstalling NET core 6.0 and 3.1. Also ran sfc /scannow with no improvements.

I'm thinking it could be helpful to go back to the version before LB switched to the newer NET core version, but I'm unsure where I would find an particular older version of LB. Is there a repository somewhere for the older versions?

 

(10/27 update):

Continuing to look into this, I searched for the specific error code I was getting. Several different resources mention a possible issue being background garbage collection, "gcConcurrent" setting used within NET core. The couple resources I found: 

 

https://learn.microsoft.com/en-us/dotnet/core/runtime-config/garbage-collector (specifically the Background GC part)

https://stackoverflow.com/questions/4367664/application-crashes-with-internal-error-in-the-net-runtime (mentions the error and it potentially having to do with garbage collection)

 

I'm now trying to see if I can change that setting within the LB runtimeconfig.json file itself. Guessing I might break something in the process, but if this extra info provides any chance of a repair it's worth it.

 

After all that, this looks to work for me. I added this to my LB runtimeconfig file and I'm not getting the crashes with updating metadata/media anymore.

{
   "runtimeOptions": {
      "configProperties": {
         "System.GC.Concurrent": false
      }
   }
}

Edited October 27 by TheNewClassics