You should be able to find the location by right clicking on eu4 in the steam library and selecting "Manage" -> "Browse local files"
- 1
Random Crashing [1.33, nomods, Mac OS]
- Thread starter Ferdinand_Bardamu
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I have done what you said, but the crashing still exists. This time in an England campaign.
I've checked the exception file and it's the Manpower thing again.
It would be really cool if someone from Paradox could help out with this. It always happens post 1500.
I've checked the exception file and it's the Manpower thing again.
It would be really cool if someone from Paradox could help out with this. It always happens post 1500.
- 1
What was the output of the sha256sum command?
To make this more reproducible for the developers, it would be helpful if you could post a few game.log files from your crashes to see if this is caused by specific events
I am struggling to get that to work exactly.
I am going to do a third clean reinstall of EU4 and see what happens. If it keeps crashing I'll keep uploading all the files and save games in this thread. Just that I've done two before and the problem persists, it's specifically a post 1.33 issue as well. I never had this on 1.32.
I have that as well
I posted my logs https://forum.paradoxplaza.com/foru...segv-error-i-am-on-mac.1514052/#post-28216290
but got redirected here. Should I post my exception.log and game.log and error.log files? In my error logs the last errors when looking after the crash all say tribal development set below 0.
I posted my logs https://forum.paradoxplaza.com/foru...segv-error-i-am-on-mac.1514052/#post-28216290
but got redirected here. Should I post my exception.log and game.log and error.log files? In my error logs the last errors when looking after the crash all say tribal development set below 0.
I think it is pretty clear by now that this seems to be a macOS specific error which is related to the installation of a particular user. I think it would be useful if one of you makes a post in the bugreports forum about this and attaches the various exception.txt files and mentions that they all crash in a manpower related effect. It might also be useful if all affected users post more details about their systems to see if they have something in common. A post in the main forum which asks if there are macOS users who are not affected might also help to narrow down the source of the problem.
You can also attach the error.log files, but I don't think that they contain anything useful, because the error.logs which I looked at, ended with different errors and had these errors already earlier in the error log without crashing and the errors are also in the log files on other OSes which don't crash.
You can also attach the error.log files, but I don't think that they contain anything useful, because the error.logs which I looked at, ended with different errors and had these errors already earlier in the error log without crashing and the errors are also in the log files on other OSes which don't crash.
My most recent crash didn't say anything about manpower...
I'll attach here the error.log, the game.log and the exceptions.log (from the crashes folder).
It does. The second line in the Demangled Stack trace contains "CYearlyManpowerEffect::Execute". All of the exception.txt which have been posted yet had some manpower effect in their second line(either CYearlyManpowerEffect::Execute or CManpowerEffect::Execute). And that manpower effect calls the function where it actually crashes(the first line). But it doesn't show a name nor in which program/library the crash happens. I don't know why that is, but it could be that the bug is that the manpower effect executes code at the wrong place in the RAM and that this memory location doesn't even contain a function. Or this is a function which gets dynamically generated. In any case the manpower effect is involved in some way.
- 1
To bring it to the attention of the developers, it would be useful to make a bugreport about this like I suggested in this comment and do the other things which I mentioned there.
I have similar crashes (2018 MBP, Big Sur 11.6.5) - I have sent reports to the developers but can upload my next crash. It's highly annoying but the crashes don't happen at the same time so simply restarting from the latest save does the trick for me.
Oh my crash had the same error.log like this, the 4 province are all the same, !!!!
I solve the problem. I see the game.log which writes like this - "For the King! the Britain Civil War beginns"( not exactly like this) at the last line of game.log at 1627.8.1 when I crashed. And I 'integrate GBR' then the crash disappeared!
And when I tag to GBR, and wait for English Civil War at 1627.8.1, and I don't click the options, the game goes well, and as long as I choose "For the King!"(which decreases manpower) at someday on August, the game crashed! @grotaclas
And when I choose For the Parliament( which also decreases manpower to a negative number, I had 3000 and this event decreases about 16000, so I got a negative number), it also crashed. I need to add manpower to GBR and it works!
The 4 errors in the history files happen on every unmodded startup on every OS and also happen in older versions. They have nothing to do with the crash.
This is very interesting. Can you test to start a new game as england, use the console command
manpower -7 to get your manpower low and then use event english_civil_war.1 to spawn the civil war event. Does it crash then when you click on the options? Can somebody else confirm that this event crashes the game?
I tried these codes, but it went well, no crashes. I don't know why... when I was playing, the problem was definetely a negative manpower, when I added some manpower to GBR, the game won't crash...
Do you still have the crashing save from before you added manpower? If you do, can you attach it here?