• 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.

Ferdinand_Bardamu

Second Lieutenant
Feb 2, 2022
195
634
Hi there,

In just about every campaign I have on 1.33, I have random crashing. There seems to be no pattern, but the game just frequently crashes especially come 1500s. Sometimes it's very frequent as in every year or two.

If someone could point me to where I can share crash logs/files I would be happy to do so.

It kinda makes the game unplayable.

Thanks!
 
When you have a crash like this, can you start the game right up, load the save, and carry on? Or does it crash in the same place?


Please attach here your Documents/Paradox Interactive/EU4/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/EU4/logs/ folder, attach here system.log , error.log .

Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.
 
When you have a crash like this, can you start the game right up, load the save, and carry on? Or does it crash in the same place?


Please attach here your Documents/Paradox Interactive/EU4/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/EU4/logs/ folder, attach here system.log , error.log .

Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.
Hello,

Thank you kindly for your response.

I am always able to continue the game, and the game won't crash on the same date but it will frequently crash at random dates.

I opted for a clean reinstall of EU4 on my computer. I should be able to report in a day or so (the problem doesn't really show up until 1500s) then.

Thanks.
 
I have the same problem: game started to crash frequently in the 1.32 version. I waited for the .33 hoping it would be more stable, but the problem only became worse. The workaround I've found is to increase the frequency of auto-saves so I don't loose more than 5 months of progress when the game crashes.

The game is not *unplayable* per se, but it's just not fun anymore, having to reload over and over and over again every few minutes.
 
When you have a crash like this, can you start the game right up, load the save, and carry on? Or does it crash in the same place?


Please attach here your Documents/Paradox Interactive/EU4/settings.txt and pdx_settings.txt .
From your Documents/Paradox Interactive/EU4/logs/ folder, attach here system.log , error.log .

Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.

Hi,

Was just having a tall chill France game for fun to test if my game was working correctly and come 1500s it crashed again.

Here are the details below:

@grotaclas
 

Attachments

  • system.log
    5,9 KB · Views: 0
  • error.log
    35,1 KB · Views: 0
  • exception.txt
    3 KB · Views: 0
The exception.txt indicates that somebody(presumably the AI) clicks on an event option which does something with manpower (probably add_yearly_manpower). Do you still have the game.log from that crash? It might reveal the event which happend(but it could also be that it crashed before writing the event to the log).

If you load your game again, does it crash again or can you continue for a longer time? If it crashes again, is "CYearlyManpowerEffect::Execute" again near the top of the Demangled Stack Trace? If you have a save which reproducible crashes, you could attach it here and I can try if it also crashes for me.

Are you using any mods? If you do, does it help if you disable all of them?

Disclaimer: I'm not working for Paradox. I'm just trying to help people.
 
  • 1Like
Reactions:
The exception.txt indicates that somebody(presumably the AI) clicks on an event option which does something with manpower (probably add_yearly_manpower). Do you still have the game.log from that crash? It might reveal the event which happend(but it could also be that it crashed before writing the event to the log).

If you load your game again, does it crash again or can you continue for a longer time? If it crashes again, is "CYearlyManpowerEffect::Execute" again near the top of the Demangled Stack Trace? If you have a save which reproducible crashes, you could attach it here and I can try if it also crashes for me.

Are you using any mods? If you do, does it help if you disable all of them?

Disclaimer: I'm not working for Paradox. I'm just trying to help people.
You are a massive help to the whole community.

The issue is the game.log must have been written over as I continued playing just fine after. This is the weird thing about my crashing issues, they're completely random.

It could crash on say August 4th 1504, I reload it and play that date fine but then January 30th 1508 it crashes again. So trying to replicate the crash is hard.

In this game I was playing atypically for me. I'll attempt to have another game in which I play more typically and then share the file/logs with you. I say this because I am certain last time missionary conversions were causing crashes and in this game I was tall.
 
  • 1
Reactions:
The issue is the game.log must have been written over as I continued playing just fine after.
yeah, the game.log gets overwritten each time you start eu4.
This is the weird thing about my crashing issues, they're completely random.
Try to collect logs from more crashes(especially exception.txt and game.log). Maybe a pattern emerges.
 
These are all manpower related effects. Your first exception.txt had CYearlyManpowerEffect and the last two had CManpowerEffect Did you check the game.log if it mentions an event at the end which has such an effect? How frequent are your crashes? Can you attach the save game?
 
These are all manpower related effects. Your first exception.txt had CYearlyManpowerEffect and the last two had CManpowerEffect Did you check the game.log if it mentions an event at the end which has such an effect? How frequent are your crashes? Can you attach the save game?
Both error.log's had this:

[persistent.cpp:87]: Parsing Error. File: "history/provinces/2585 - Kichesipi.txt", Error: Malformed token: NO, near line: 27, Last good read: controller=---
[persistent.cpp:87]: Parsing Error. File: "history/provinces/2586 - Tionontate.txt", Error: Malformed token: NO, near line: 34, Last good read: controller=---
[persistent.cpp:87]: Parsing Error. File: "history/provinces/988 - Huron.txt", Error: Malformed token: NO, near line: 35, Last good read: controller=---
[persistent.cpp:87]: Parsing Error. File: "history/provinces/989 - Ontario.txt", Error: Malformed token: NO, near line: 28, Last good read: controller=---

Does it mean anything?

I have loaded the game since the crash, is the game.log still relevant?

Here's the save file. It crashes around once or twice every 10 years although the crashing on this game has been a lot less frequent than my last games.

I appreciate you taking the time to help me @grotaclas @AndrewT
 

Attachments

  • Delhi.eu4
    7,5 MB · Views: 0
I ran your save twice for over twenty years and it didn't crash for me. I'm using Linux and not macOS which could play a role, but I think it's more likely that it is still some problem with your game installation.
Which checksum is displayed in your main menu?(the checksum in the launcher doesn't count)

The messages in the error.log are harmless. Everybody gets them, because there is a wrong line in these files. But the line is for later start dates, so even if it has any impact, it would not happen for games which were started in 1444.

Did you get more crashes and save the game.log files from them?
 
  • 1Like
Reactions:
I ran your save twice for over twenty years and it didn't crash for me. I'm using Linux and not macOS which could play a role, but I think it's more likely that it is still some problem with your game installation.
Which checksum is displayed in your main menu?(the checksum in the launcher doesn't count)

The messages in the error.log are harmless. Everybody gets them, because there is a wrong line in these files. But the line is for later start dates, so even if it has any impact, it would not happen for games which were started in 1444.

Did you get more crashes and save the game.log files from them?
The checksum seems accurate. Up to date.

Do you know where the 'correct' place for Mac files to be installed is? Wonder if they've ended up in the wrong place.
 
The checksum seems accurate. Up to date.
What is the exact checksum in the main menu? Can you post a screenshot of the main menu?

Do you know where the 'correct' place for Mac files to be installed is? Wonder if they've ended up in the wrong place.
I don't think that there is a "correct" place. You can configure different installation locations in steam and they should all work. If it is not installed correctly, the game could not start at all and if there were game files missing, the checksum would change(that's why I'm asking about it).
 
What is the exact checksum in the main menu? Can you post a screenshot of the main menu?


I don't think that there is a "correct" place. You can configure different installation locations in steam and they should all work. If it is not installed correctly, the game could not start at all and if there were game files missing, the checksum would change(that's why I'm asking about it).
It says exactly this:

EU4 v1.33.2.0 France
(108e)

Any use?

I really, really appreciate your help btw.
 
EU4 v1.33.2.0 France
(108e)
That's the correct checksum, so the normal game files are correct. It could still be that eu4.app is broken in a small way, but this is unlikely(the eu4 executable is not covered by the checksum). You could try to verify the integrity of the game files in steam to see if it finds anything. Or you could verify the sha256 checksum of the files. You can do this by downloading the file eu4_macOS_1.33.2.sha256.txt which I attached to this post to the folder where eu4 is installed and then open a terminal window(a command line) in that folder and then run the following command to verify the checksum of the macOS specific game files:
Code:
sha256sum -c eu4_macOS_1.33.2.sha256.txt
The command should output one filename per line and an "OK" at the end of the line if the file on your computer matched the checksum. The file eu4_macOS_1.33.2.sha256.txt contains the checksums for all the macOS specific game whiles which I downloaded with steam. But I don't have macOS myself, so I don't know if they are actually correct and I don't know how to run command line programs in macOS.

Did you continue playing and got more crashes and if you did, did you save the game.log files from the crashes?
 

Attachments

  • eu4_macOS_1.33.2.sha256.txt
    2,2 KB · Views: 0
Hi, I have read through this thread and it appears I am encountering the very same issue, with the same game version (the latest 1.33.2 (108e))
I'm running the game on a Mac, and at a seemingly random time, there is a crash. When looking into the logs, it's the very same issue related to some manpower method/function.
I'm running a very old MacOS version (X.13.6)
You can always restart the game from an autosave, but the crash will happen at some point.
It looks like it's a platform specific issue: if ever this problem was occurring on windows, there would have been dozens of people reporting this problem. But here we are, there is thread on a crash with specific symptoms and the 2 people reporting it are running macOS.
I think the crash reporter of EUIV already sent relevant files to Paradox, but here some of them
 

Attachments

  • exception.txt
    3 KB · Views: 0
  • game.log
    440,1 KB · Views: 0
  • error.log
    21 KB · Views: 0
  • system.log
    6,4 KB · Views: 0
  • ProteosLithuania.eu4
    5,9 MB · Views: 0
  • 1Like
Reactions:
@grotaclas

One of the issues I've had since doing a clean reinstall is that I can't even locate where EU4 is installed. It isn't in the usual place Steam games usually go.

@Proteos

Sorry to hear you are having the same problem. I know that Paradox made a mistake when 1.33 first came out which made it impossible for the game to launch. I wonder if there isn't an error somewhere in the way 1.33 works with Macs. I never had this problem on 1.32.

It'd be really great if someone from Paradox could get on this @AndrewT