getInfoTypeForString is supposed to map a <Type> string from XML - like "UNIT_AXEMAN" - to a DLL-internal ID. Usually gets called by Python code, for example
here by the WBSave parser to look up "CIVIC_..." strings found in a WBSave file. Apart from civics, the parser looks up state religions and start eras. So maybe it's worth checking whether your WBSave assigns empty strings to any of those. Oh, but the parser also looks up lots of other type strings via findInfoTypeNum in CvUtil.py:
So any line with ...Type=
(nothing) could be responsible. Maybe the problem will become more apparent if you just ignore the failed assertion? Anything in PythonErr.log if you do so? It might also help to adopt
this bugfix to the pyAssert function. That function is supposed to write a Python stacktrace to PythonErr.log when findInfoTypeNum fails, but it's incorrectly implemented and just silently ignores the failure instead. A more reliable way to get a Python exception would be to (temporarily) change getInfoTypeForString in the DLL so that it crashes the DLL rather than show a failed-assertion popup. But that will require recompilation of the DLL.