Conflict Solver on large collections gives errors or silent crashes

[Justist]

Describe the bug
I have a collection of 87 Stellaris mods which, when merged, total at about 5.2 GB. When I try to use the conflict solver function, in any option (analyze, default, or advanced) it causes Irony to either silently crash (most of the time) or give an error (as attached). The silent crashes happen at step 1 or 3, the error happened at step 5.

For a smaller modlist the behaviour is as expected.

To Reproduce
Steps to reproduce the behavior:
0. Select Stellaris as a game

1. Have a large mod list
2. Press the button "Conflict Solver" in the bottom right.
3. Wait
4. See if it crashes

Expected behavior
Conflict solver fullfills its progress and shows me the conflicts editor.

Screenshots

Logs
Error:
ironybug23042026.txt
Stellaris modlist:
ironymodlist.json
Error log:
2026-04-23_Error.log

Version:

• OS: Windows 11
• Irony Version: 1.27.172

Additional context
I uninstalled and reinstalled Irony earlier today, and also removed the IndexCache folder in \AppData\Roaming\Mario\IronyModManager

Noteworthy addition:
When trying to apply modlists, I get a "Save Error" notifying me that something is blocking the writing to mod files. This however happens for every of my mod lists in Irony, and is not logged in the error.log file.

[bcssov]

First, regarding the crash: the exception suggests some unusual behavior. Are you running Irony CS on a merged collection, and how much RAM is available on your system? An NRE at that point is not typical and may indicate an environmental issue such as memory pressure or data inconsistency rather than a straightforward application bug.

As for the save error, the log shows that a string value is being written into the SQLite datetime field:

System.FormatException: The input string '2026-04-09 12:19:14' was not in a correct format.

This format does not match what Irony expects. According to the Paradox playsets database schema, the column is defined as:

CREATE TABLE playsets (
    ...
    pdxUserId   CHAR (36),
    createdOn   DATETIME NOT NULL,

While SQLite itself is permissive with stored values, Irony follows the format used by Paradox, which is a Unix epoch integer representation:

Convert.ToInt64((input - DateTime.UnixEpoch).TotalMilliseconds);

I've verified this against the latest Paradox beta branch, and the schema has not changed.

In Irony, the field is mapped and handled as:

[Map("createdOn"), PropertyHandler(typeof(LongToDateTimeHandler))]
public DateTime CreatedOn { get; set; }

So the current error likely stems from the database containing data that does not conform to the expected format.

[Justist]

To answer the questions:

1. Regular collection. Performed a merge only to see the total size of the mods.
2. 192GB. Should be enough, does look like it only uses a little anyway.
3. Save error: Had some playsets with faulty dates indeed, deleted them. After that, applying also works again.

Then the conflict solver worked for my given dataset. Tried it a few times, no crashing or errors.

However.
Then I created 4 new playsets in the launcher, 3 of which I gave above 200 mods and one empty.
After that I ran the conflict solver again.
Now Irony Mod Manager crashes on step 1/6 again, with no file generated in the %APPDATA%\Roaming\Mario\IronyModManager-Logs folder.

Here are the playsets with their createdOn fields (just to make sure they are now in the right format):

And here are the mod counts per playset:

[bcssov]

Irony logs all runtime errors. Since no log was generated, this likely points to an external cause rather than an internal error.
Check Windows Event Viewer as it looks like the process may have been terminated externally.

[Justist]

The event viewer does indeed show that Windows kills it, for attempting to read or write protected memory.
My logs:
ironyerroreventviewer1.txt
ironyerroreventviewer2.txt

As this only happens when I have large playsets present in the launcher, maybe there is some memory corruption going on when/if Irony interacts with the sqlite file?

[bcssov]

This is a native/runtime crash inside the CWTools/FParsec parser, not a normal managed Irony exception.
Irony cannot log it because the process terminates at the CLR level.
Please isolate which mod/file triggers the crash and provide a minimal repro.