Mid-battle CTD, game is generally unstable

Hey,
I just installed the game (EBII 2.2b+2.2q+listed fixes) and coming back as a longtime EB1.2 player felt great. Looking at how complex recruitment, etc. has become, the mod went a long way from EB1.2's static "homeland" and "expansion regions" and type I-IV government types. Great work, a big thanks to everyone working on the project!
However, in my case the mod runs generally quite unstable. Yesterday evening I tried a Carthage campaign, where it crashed when I loading my first battle against some rebels in Sicily. Today I tried a Pergamon campaign, where it crashed in turn 1 in the middle of some battle against some Galatian raiders (for that one you find the log file attached). I also encountered the UI bug I knew from an earlier build.
From what I remember, I closely followed the instructions for both installations, but given how unstable the game runs I feel like I missed some major point. Is there some kind of standard troubleshooting procedure / list of typical bugs and how to solve them?

I am using a disc version of MTW2 and Kingdoms, both of which seem to run fine. OS is Windows 10.

Thanks for your help!

Nothing but regular trace in there; did you change the error logging method to only report errors, not all trace, for normal running? That has a big impact on stability and performance by itself.

There are also memory-related issues you need to research solutions to.

Hi,
thanks for the hint on the memory issue. That has significantly increased stability. Gave it another shot yesterday evening, game ran stable for almost two hours until I once again encountered the UI bug with a subsequent crash.
Regarding the log: The installation guide for 2.2b says it should be set to "trace". You might want to edit that if it increases stability. I will change that and see later whether that makes my build more stable. In any case, the mod seems to be playable now- Thanks for the hint!

If your session runs long enough, you will eventually hit a memory leak. Every action increases memory usage, so it is inevitable.

That advice in the 2.2b thread has been superceded; while it's useful to have trace enabled when you encounter a recurring CTD, at all other times you should only have error enabled.