Unfortunately, as expected for a crash, the lua log doesn't help much: they're useful for lua errors because those ones write informations about what turned wrong. But for crashes it just tell me roughly after which point it crashed.
Here is what I suggest: locate the IGE_window.xml file in IGE folder. Open it with a regular text editor. Locate this part:
What you need to do is to comment out (or remove) every "LuaContext" entry to prevent IGE to start those modules. Commenting is done that way (must start with <!-- and ends with -->):
So you start with all of them commented out, then you restore entries until you find the one causing the crash. And, of course, even if civ5 does not crash, you need to restart it anytime you change that file. That would not be fun otherwise. I strongly suggest you actually devise a method like start with the first 8 commented out and the 8 others intact, then the opposite, then use groups of 4, etc.
I know it's quite a painful work, trust me, I'm far too much used to that. But civ5 is a giant pile of bugs and if it crashes then it's civ5's fault. Me, I can only find a way to circumvent it. And without a mac, I cannot find it myself.
Now I would understand if you do not feel like going through such a pain just to use IGE. Especially because, actually, once we found the troublesome module (LuaContext), unless you're fine with totally disabling it, we will have to go though additional steps to find the very troublesome part. With no guarantee I will be able to circumvent the bug.
So it's up to you: suffer and help me fix IGE or wait for Firaxis to fix their game on macs, which could happen before 2018. I am sorry I do not have any better alternative.
Here is what I suggest: locate the IGE_window.xml file in IGE folder. Open it with a regular text editor. Locate this part:
Code:
<Container ID="PanelsContainer" Offset="0,63" Size="1286,410">
<LuaContext FileName="IGE_ActivePlayerSelection" ID="ActivePlayerSelection" />
<LuaContext FileName="IGE_TerrainPanel" ID="TerrainPanel" />
<LuaContext FileName="IGE_CitiesPanel" ID="CitiesPanel" />
<LuaContext FileName="IGE_UnitsPanel" ID="UnitsPanel" />
<LuaContext FileName="IGE_PlayersPanel" ID="PlayersPanel" />
<LuaContext FileName="IGE_TechsPanel" ID="TechsPanel" />
<LuaContext FileName="IGE_PoliciesPanel" ID="PoliciesPanel" />
</Container>
</Box >
</Grid>
<!-- Bulk UI over panel -->
<Container Size="F,F" ID="BulkUI_Over">
<LuaContext FileName="IGE_AlertStack" ID="AlertStack" />
<LuaContext FileName="IGE_ProductionPopup" ID="ProductionPopup" Hidden="1"/>
<LuaContext FileName="IGE_ConfirmPopup" ID="ConfirmPopup" Hidden="1"/>
<LuaContext FileName="IGE_ChooseReligionPopup" ID="ChooseReligionPopup" Hidden="1"/>
<LuaContext FileName="Assets/UI/InGame/TopPanel" ID="TopPanel"/>
<LuaContext FileName="IGE_WonderPopup" ID="WonderPopup" Hidden="1"/>
</Container>
</Container>
What you need to do is to comment out (or remove) every "LuaContext" entry to prevent IGE to start those modules. Commenting is done that way (must start with <!-- and ends with -->):
Code:
<!--LuaContext FileName="IGE_WonderPopup" ID="WonderPopup" Hidden="1"/-->
So you start with all of them commented out, then you restore entries until you find the one causing the crash. And, of course, even if civ5 does not crash, you need to restart it anytime you change that file. That would not be fun otherwise. I strongly suggest you actually devise a method like start with the first 8 commented out and the 8 others intact, then the opposite, then use groups of 4, etc.
I know it's quite a painful work, trust me, I'm far too much used to that. But civ5 is a giant pile of bugs and if it crashes then it's civ5's fault. Me, I can only find a way to circumvent it. And without a mac, I cannot find it myself.

Now I would understand if you do not feel like going through such a pain just to use IGE. Especially because, actually, once we found the troublesome module (LuaContext), unless you're fine with totally disabling it, we will have to go though additional steps to find the very troublesome part. With no guarantee I will be able to circumvent the bug.
So it's up to you: suffer and help me fix IGE or wait for Firaxis to fix their game on macs, which could happen before 2018. I am sorry I do not have any better alternative.
