SMAPI fails (Internal CLR Error 0x80131506) if it is unable to call home.

[Nox13last]

Discussion and eventual conclusion: https://discord.com/channels/137344473976799233/1478869777609916497/1478869777609916497

Describe the bug
If SMAPI attempts to make queries for updates regarding itself or its blacklist, but doesn't receive a valid reply, the application bombs.
I experienced this issue with Pi-Hole. Closing it - or disconnecting my internet gateway - fixes the issue.

Upon nullifying the following parameters in \smapi-internal\config.json:

• GitHubProjectName
• WebApiBaseUrl
• BlacklistUrl
  ...THEN it works

To Reproduce
Exact steps which reproduce the bug, if possible. For example:
Pre-requisite: Pi-Hole or any other sort of custom DNS infrastructure that governs the user's internet connection strictly.

1. Open StardewModdingAPI.exe Program bombs before the game opens.
2. Nullify the above parameters
3. Open StardewModdingAPI.exe again. Game reaches main menu successfully.

Log file does not contain any errors. Last two lines:

[21:33:53 TRACE SMAPI] Checking for updates...
[21:33:53 WARN  SMAPI] Couldn't check for a new version of SMAPI. This won't affect your game, but you won't be notified of new versions if this keeps happening.

[Pathoschild]

Hi! SMAPI itself doesn't need update checks to work. Those happen in a background thread which just logs any errors:

catch (Exception ex)
{
    this.Monitor.Log("Couldn't check for a new version of SMAPI. This won't affect your game, but you won't be notified of new versions if this keeps happening.", LogLevel.Warn);
    this.Monitor.Log(ex is WebException && ex.InnerException == null
        ? $"Error: {ex.Message}"
        : $"Error: {ex.GetLogSummary()}"
    );
}

However, the log file you posted on Discord ends here:

[21:33:53 TRACE SMAPI] Checking for updates...
[21:33:53 WARN SMAPI] Couldn't check for a new version of SMAPI. This won't affect your game, but you won't be notified of new versions if this keeps happening.

Note that the exception info line is missing. That means that the app somehow crashed to desktop when it tried to log the exception info.

This tentatively seems like a bug in the underlying .NET Framework or OS/drivers, since...

• SMAPI should intercept crashes;
• this code is running in a background thread separate from the game process;
• and your title mentions internal CLR error 0x80131506, which is apparently a low-level runtime corruption error (which can't be caught by app code).

Can you do this to provide more info?

1. Open the Event Viewer in Windows.
2. From the sidebar, go to Custom Views > Administrative Events.
3. Cause the SMAPI crash again.
4. Refresh Event Viewer.
5. Post a screenshot of any relevant Warning or Error event that got logged.

[Nox13last]

Done. I have two.

Event 1023, .Net Runtime
Application: StardewModdingAPI.exe
CoreCLR Version: 6.0.3224.31407
.NET Version: 6.0.32
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFFCE5B4659 (00007FFFCE540000) with exit code 80131506.

Event 1000, Application Error
Faulting application name: StardewModdingAPI.exe, version: 4.5.1.0, time stamp: 0x670d0000
Faulting module name: coreclr.dll, version: 6.0.3224.31407, time stamp: 0x666c84f2
Exception code: 0xc0000005
Fault offset: 0x0000000000074659
Faulting process id: 0x2C64
Faulting application start time: 0x1DCAD01E1546EA1
Faulting application path: D:\SteamLibrary\steamapps\common\Stardew Valley\StardewModdingAPI.exe
Faulting module path: D:\SteamLibrary\steamapps\common\Stardew Valley\coreclr.dll
Report Id: bcf901de-3cb6-4818-83f2-86aa81351326
Faulting package full name:
Faulting package-relative application ID:

[Pathoschild]

Yep, this seems like a crash in the .NET runtime, unrelated to SMAPI itself. The CoreCLR version is correct, so it might be a .NET bug related to something else on your system (e.g. a crash when security software intercepts HTTP requests).

Can you come ask in #modded-tech-support on the Stardew Valley Discord so we can run some tests? I'll close this since it seems like a system bug (unrelated to SMAPI), but feel free to ping me on Discord with @pathoschild if you don't get an answer there.