Crash when click family tree

So I hadn't a single crash since the new log cfg method, until a little while ago. I forgot exactly what I was doing when it crashed but I assumed my luck had run out. Then luckily (unluckily) it crashed again, this time I realized it was when I'd clicked family tree. So I tried again and, yup, it's repeatable. Must have started being a thing relatively recently, just under 400 turns in.

Nothing useful in the reduced log; can you switch to trace, repeat the error, then post that log?

There is a bug where the game can simply no longer load the amount of portraits in the family tree due to memory issues, not sure if that is what you're encountering though.

It may well be as you say, z3n (even though I do use 4gb access). When I changed logging back to trace, it didn't crash. Initially. But after I clicked it a few times to test, I got the graphical corruption memory leak thing and quit/crash. Before switching to trace, I tried repeating it again on a different turn and the first click didn't crash, but the second did.

This is pretty bad news for me if I can't access family trees moving forward as I consult it all the time to figure out which family chunks get which tracts of lands, running a kind of feudal family line system dividing the empire into dynastic partitions, plus other decision making that depends on who's who... I might have to start keeping track of this stuff manually outside of the game...

The graphical corruption is a pretty telltale sign; that's memory leak and if you've already done everything you can to mitigate it, there's nothing else that can be done.

Does default M2TW never get to a point where family trees get so extensive this happens? Seems like a pretty serious design flaw if the game can't handle a core mechanic after a while. Though I can see if the mod introduces elements that weren't anticipated that contribute to either larger family trees or overall less memory to go around because used up elsewhere or something.

Unfortunately, I think it's a facet of the amount EBII specifically strains the upper limits of what the engine can do. I don't think vanilla has a problem because it has simpler scripts and less draw on memory generally.