Game Crash/Freeze on Mac

[♎ Hannibal M. Barca (ÞØWER)]

Hello guys, since around yesterday the game keeps on crashing or rather freezing with the colourful cursor symbol just going around in circles/rotating. I have updated to the newest OS since then without effect, verified integrity of game files both before and after the update but nothing seems to help. It happens on old saves and newly started ones. After 2-10 minutes this occurs.
Hopefully someone can help.

[grotaclas]

Does the game create a new folder in "Documents/Paradox Interactive/Europa Universalis IV/crashes"? If it does, can you please post the exception.txt from that folder

[♎ Hannibal M. Barca (ÞØWER)]

Application: EUIV
Version: EU4 v1.37.5.0 Inca
Date/Time: 2024-11-07 10:54:28

Caught signal 11 (SIGSEGV)

Original Stack Trace:
2 ??? 0x0000000000000000 0x0 + 0
3 eu4 0x000000010093719f _ZN11CDependency9OnDisableEbb + 179
4 eu4 0x000000010093705d _ZN11CDependency8TransferE11CCountryTagS0_ + 37
5 eu4 0x00000001002b8970 _ZN8CCountry14ClearRelationsE11CCountryTag + 2520
6 eu4 0x00000001002b9e6e _ZN8CCountry22NotifyLostLastProvinceE11CCountryTag + 2660
7 eu4 0x00000001008e14ce _ZN9CProvince8SetOwnerERKNS_19SSetOwnerParametersE + 4802
8 eu4 0x00000001008ee21d _ZN9CProvince7ConquerE11CCountryTagRK8CEU3DatePKcbRK14SConquerParams + 633
9 eu4 0x0000000100248950 _ZN8CCountry5AnnexE11CCountryTagbbbbbb + 2828
10 eu4 0x000000010085560e _ZN11CPeaceOffer13Execute_AnnexER6CArrayINSt3__14pairI11CCountryTagS3_EEE + 1404
11 eu4 0x0000000100850694 _ZN11CPeaceOffer7ExecuteEv + 6052
12 eu4 0x00000001004ca04d _ZNK19CRequestPeaceAction14ExecuteDerivedEv + 5411
13 eu4 0x0000000100413362 _ZNK17CDiplomaticAction7ExecuteEv + 178
14 eu4 0x00000001004160d4 _ZNK24CDiplomaticActionCommand7ExecuteEv + 1362
15 eu4 0x000000010141f159 _ZNSt3__110__function6__funcIZL18ExecuteWithPaddingRK8CCommandE3$_1NS_9allocatorIS5_EEFvvEEclEv + 157
16 eu4 0x000000010143b8ff _ZL16CallstackPaddingRKNSt3__18functionIFvvEEEj + 47
17 eu4 0x000000010143b8be _ZN10CRandomLog16CallstackPaddingERKNSt3__18functionIFvvEEE + 46
18 eu4 0x000000010141c3c3 _ZN8CSession15ProcessCommandsEv + 577
19 eu4 0x000000010141bb14 _ZN8CSession6UpdateEv + 328
20 eu4 0x0000000100157ba9 _ZN15CEU4Application6UpdateEv + 109
21 eu4 0x0000000100708b47 _ZN12CInGameIdler4IdleEb + 1683
22 eu4 0x00000001013ca2a0 _ZN12CApplication14UpdateOneFrameEb + 288
23 eu4 0x00000001013ca74a _ZN12CApplication3RunEv + 48
24 eu4 0x0000000100755aea main + 10944
25 dyld 0x000000020303b366 start + 1942

Demangled Stack Trace:
2 ??? 0x0000000000000000 0x0 + 0
3 eu4 0x000000010093719f CDependency::OnDisable(bool, bool) + 179
4 eu4 0x000000010093705d CDependency::Transfer(CCountryTag, CCountryTag) + 37
5 eu4 0x00000001002b8970 CCountry::ClearRelations(CCountryTag) + 2520
6 eu4 0x00000001002b9e6e CCountry::NotifyLostLastProvince(CCountryTag) + 2660
7 eu4 0x00000001008e14ce CProvince::SetOwner(CProvince::SSetOwnerParameters const&) + 4802
8 eu4 0x00000001008ee21d CProvince::Conquer(CCountryTag, CEU3Date const&, char const*, bool, SConquerParams const&) + 633
9 eu4 0x0000000100248950 CCountry::Annex(CCountryTag, bool, bool, bool, bool, bool, bool) + 2828
10 eu4 0x000000010085560e CPeaceOffer::Execute_Annex(CArray<std::__1::pair<CCountryTag, CCountryTag>>&) + 1404
11 eu4 0x0000000100850694 CPeaceOffer::Execute() + 6052
12 eu4 0x00000001004ca04d CRequestPeaceAction::ExecuteDerived() const + 5411
13 eu4 0x0000000100413362 CDiplomaticAction::Execute() const + 178
14 eu4 0x00000001004160d4 CDiplomaticActionCommand::Execute() const + 1362
15 eu4 0x000000010141f159 std::__1::__function::__func<ExecuteWithPadding(CCommand const&)::$_1, std::__1::allocator<ExecuteWithPadding(CCommand const&)::$_1>, void ()>::operator()() + 157
16 eu4 0x000000010143b8ff CallstackPadding(std::__1::function<void ()> const&, unsigned int) + 47
17 eu4 0x000000010143b8be CRandomLog::CallstackPadding(std::__1::function<void ()> const&) + 46
18 eu4 0x000000010141c3c3 CSession::ProcessCommands() + 577
19 eu4 0x000000010141bb14 CSession::Update() + 328
20 eu4 0x0000000100157ba9 CEU4Application::Update() + 109
21 eu4 0x0000000100708b47 CInGameIdler::Idle(bool) + 1683
22 eu4 0x00000001013ca2a0 CApplication::UpdateOneFrame(bool) + 288
23 eu4 0x00000001013ca74a CApplication::Run() + 48
24 eu4 0x0000000100755aea main + 10944
25 dyld 0x000000020303b366 start + 1942

[♎ Hannibal M. Barca (ÞØWER)]

Originally posted by grotaclas:

Does the game create a new folder in "Documents/Paradox Interactive/Europa Universalis IV/crashes"? If it does, can you please post the exception.txt from that folder

Posted the most recent one there are several from today though

[grotaclas]

That's one of the most common crashes in the current version on macOS(for some reason it is rare on windows). It happens in some cases when a country which has a subject gets fully annexed in a war. In all the cases which I have seen, the subject had its independence supported by another country. Is that also the case in your save?

You got that 2-10 minutes into a new save? Are you just playing on speed 5? A common case is that Byzantium gets annexed by the Ottomans while they have Athens as a subject which got disloyal because they were turned into a pronoiar. But that usually takes a few ingame years.

[♎ Hannibal M. Barca (ÞØWER)]

It first occurred while playing Byzantium actually before starting a new save as Aztecs just to try it out but same thing began happening after the first couple of months or years in game, and now re-happens every time I restart after a few minutes.

[grotaclas]

Have you checked which wars are triggering it in your games? And did you check if all your exception.txt files have the same functions at the top of the "Demangled Stack Trace"? It could be that some of your crashes from other campaigns have other reasons, because I don't think that it is possible to get this problem a few ingame months after starting a new campaign.

I know the following workarounds for the annexation crash:
* play past the date of the crash on the windows version of the game(either on a windows system or by running the windows version on macOS with the whisky app(or another version of wine).
* use version 1.37.2 which did not have this particular crash(but more other bugs)
* use console commands to prevent the crashing peace deal
* try it a bunch of times, because there is a random element and some of the crashes don't always happen

[♎ Hannibal M. Barca (ÞØWER)]

Originally posted by grotaclas:

Have you checked which wars are triggering it in your games? And did you check if all your exception.txt files have the same functions at the top of the "Demangled Stack Trace"? It could be that some of your crashes from other campaigns have other reasons, because I don't think that it is possible to get this problem a few ingame months after starting a new campaign.

I know the following workarounds for the annexation crash:
* play past the date of the crash on the windows version of the game(either on a windows system or by running the windows version on macOS with the whisky app(or another version of wine).
* use version 1.37.2 which did not have this particular crash(but more other bugs)
* use console commands to prevent the crashing peace deal
* try it a bunch of times, because there is a random element and some of the crashes don't always happen

They all seem to have Demangled Stack Trace in the doc so must be that, but is it likely that the same thing is doing it in two different games at such different times? In my byz run I was around 1550 while in Aztec I was in 1450s. I will try going back to the previous version to see if that helps, did not have any issues on that. I have tried the byz game 5/6 times and the other one 4/5 times.
Thanks for your help

[grotaclas]

Originally posted by ♎ Hannibal M. Barca (ÞØWER):

They all seem to have Demangled Stack Trace in the doc so must be that

"Demangled Stack Trace" is the heading. I meant the lines in that section of the file. The first line is the function in which the game is crashing, so in this case it is "2 ??? 0x0000000000000000 0x0 + 0" which means it is crashing in the attempt to call a function at the address 0 which is not allowed, because it is reserved for the system. So the actual crashing function is "CDependency::OnDisable" from the next line. And that function got called from "CDependency::Transfer" which got called from "CCountry::ClearRelations" and so on. If these functions are all present in the first few lines of the "Demangled Stack Trace", it is the same crash.

Originally posted by ♎ Hannibal M. Barca (ÞØWER):

is it likely that the same thing is doing it in two different games at such different times?

This bug needs relatively specific circumstances and it doesn't always crash in those circumstances. But it seems to be quite common on macOS.

Originally posted by ♎ Hannibal M. Barca (ÞØWER):

In my byz run I was around 1550 while in Aztec I was in 1450s. I will try going back to the previous version to see if that helps, did not have any issues on that. I have tried the byz game 5/6 times and the other one 4/5 times.

That's very different from your previous claim that it happens within a few months or 2-10 minutes after the start of a new campaign.

[♎ Hannibal M. Barca (ÞØWER)]

Originally posted by grotaclas:

Originally posted by ♎ Hannibal M. Barca (ÞØWER):

They all seem to have Demangled Stack Trace in the doc so must be that

"Demangled Stack Trace" is the heading. I meant the lines in that section of the file. The first line is the function in which the game is crashing, so in this case it is "2 ??? 0x0000000000000000 0x0 + 0" which means it is crashing in the attempt to call a function at the address 0 which is not allowed, because it is reserved for the system. So the actual crashing function is "CDependency::OnDisable" from the next line. And that function got called from "CDependency::Transfer" which got called from "CCountry::ClearRelations" and so on. If these functions are all present in the first few lines of the "Demangled Stack Trace", it is the same crash.

Originally posted by ♎ Hannibal M. Barca (ÞØWER):

is it likely that the same thing is doing it in two different games at such different times?

This bug needs relatively specific circumstances and it doesn't always crash in those circumstances. But it seems to be quite common on macOS.

Originally posted by ♎ Hannibal M. Barca (ÞØWER):

In my byz run I was around 1550 while in Aztec I was in 1450s. I will try going back to the previous version to see if that helps, did not have any issues on that. I have tried the byz game 5/6 times and the other one 4/5 times.

That's very different from your previous claim that it happens within a few months or 2-10 minutes after the start of a new campaign.

Sorry I meant that it began on the Byz save after some playtime and then it reoccurs every couple of minutes when I reboot since it happened first, then I tried a new game (Aztec) where it began occurring from the onset of the new save basically or within the first couple of years and then also does it every few minutes.

[grotaclas]

Once you encounter a crashing situation, it is normal that it will crash again when the save reaches the same state. If the war is already won in the save, it usually crashes on the same date. But if there is a siege which needs to complete, it would crash shortly after that happens, which might take a few months

[934andy]

Originally posted by grotaclas:

Have you checked which wars are triggering it in your games? And did you check if all your exception.txt files have the same functions at the top of the "Demangled Stack Trace"? It could be that some of your crashes from other campaigns have other reasons, because I don't think that it is possible to get this problem a few ingame months after starting a new campaign.

I know the following workarounds for the annexation crash:
* play past the date of the crash on the windows version of the game(either on a windows system or by running the windows version on macOS with the whisky app(or another version of wine).
* use version 1.37.2 which did not have this particular crash(but more other bugs)
* use console commands to prevent the crashing peace deal
* try it a bunch of times, because there is a random element and some of the crashes don't always happen

thank you for helping with the issue. I was having a similar issue to OP, also on Mac. The Byzantium-Athens-Ottomans was precisely the issue here. I triggered a game crashing peace deal via console to confirm and the game crashed. The different dates were caused by the siege progress just as you've mentioned. for me it's happening at the 1450s mark. I'm not sure if there would be any use for my crash reports but if you'd need them I can upload them too.

[♎ Hannibal M. Barca (ÞØWER)]

Originally posted by 934andy:

Originally posted by grotaclas:

Have you checked which wars are triggering it in your games? And did you check if all your exception.txt files have the same functions at the top of the "Demangled Stack Trace"? It could be that some of your crashes from other campaigns have other reasons, because I don't think that it is possible to get this problem a few ingame months after starting a new campaign.

I know the following workarounds for the annexation crash:
* play past the date of the crash on the windows version of the game(either on a windows system or by running the windows version on macOS with the whisky app(or another version of wine).
* use version 1.37.2 which did not have this particular crash(but more other bugs)
* use console commands to prevent the crashing peace deal
* try it a bunch of times, because there is a random element and some of the crashes don't always happen

thank you for helping with the issue. I was having a similar issue to OP, also on Mac. The Byzantium-Athens-Ottomans was precisely the issue here. I triggered a game crashing peace deal via console to confirm and the game crashed. The different dates were caused by the siege progress just as you've mentioned. for me it's happening at the 1450s mark. I'm not sure if there would be any use for my crash reports but if you'd need them I can upload them too.

After starting a brand new game this time as Timurids I have made it through that point without issue. When it first occured in my Byz game it must have been a different but similar issue cause it occured in 1500s and I was already past Ottomans and also did not get annexed.