out of memory crash

[jtgasv (OP)]

during large scale ground invasions 4mil tons vs 4+mil tons
the game log bloats to a very large size and ram usage increases from 200-300mb up to 1.5gb over the course of 15 game days
closing the game and reloading does not change it and i know its the game log because im having to delete all log entries in the database every 10-15 days or so. Deleting the log brings ram use back to 200-300mb.

im not sure if this is a problem with my computer or settings. as when i asked on discord a while back 1.5gb isn't actually much ram usage for aurora.

The function number and The complete error text     - in screenshot
multiple function numbers, same error. this will be spammed endlessly and i have to end process with task manager.
The window affected    - all
What you were doing at the time     - ground invasion
Conventional or TN start     -has occurred in both (multiple saves)
Random or Real Stars     - has occurred in both (multiple saves)
Is your decimal separator a comma?     - no
Is the bug is easy to reproduce, intermittent or a one-off?     - reproduceable for me whenever i have large scale ground combat
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well     - current campaign is 463 years but happened as early as 100 years.

[Froggiest1982]

during large scale ground invasions 4mil tons vs 4+mil tons
the game log bloats to a very large size and ram usage increases from 200-300mb up to 1.5gb over the course of 15 game days
closing the game and reloading does not change it and i know its the game log because im having to delete all log entries in the database every 10-15 days or so. Deleting the log brings ram use back to 200-300mb.

im not sure if this is a problem with my computer or settings. as when i asked on discord a while back 1.5gb isn't actually much ram usage for aurora.

The function number and The complete error text     - in screenshot
multiple function numbers, same error. this will be spammed endlessly and i have to end process with task manager.
The window affected    - all
What you were doing at the time     - ground invasion
Conventional or TN start     -has occurred in both (multiple saves)
Random or Real Stars     - has occurred in both (multiple saves)
Is your decimal separator a comma?     - no
Is the bug is easy to reproduce, intermittent or a one-off?     - reproduceable for me whenever i have large scale ground combat
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well     - current campaign is 463 years but happened as early as 100 years.

The ground log is an issue I also have reported and was leading to insane amount of mb weight of the database which increases the save and loading time.

The out of memory does not surprise me also considering we are running a 32bit version and Steve hasn't release a 64 yet.

That may also fix the issue just for a bit but I really think the entry logs of ground combat should get expunged every contruction cycle.

[Droll]

during large scale ground invasions 4mil tons vs 4+mil tons
the game log bloats to a very large size and ram usage increases from 200-300mb up to 1.5gb over the course of 15 game days
closing the game and reloading does not change it and i know its the game log because im having to delete all log entries in the database every 10-15 days or so. Deleting the log brings ram use back to 200-300mb.

im not sure if this is a problem with my computer or settings. as when i asked on discord a while back 1.5gb isn't actually much ram usage for aurora.

The function number and The complete error text     - in screenshot
multiple function numbers, same error. this will be spammed endlessly and i have to end process with task manager.
The window affected    - all
What you were doing at the time     - ground invasion
Conventional or TN start     -has occurred in both (multiple saves)
Random or Real Stars     - has occurred in both (multiple saves)
Is your decimal separator a comma?     - no
Is the bug is easy to reproduce, intermittent or a one-off?     - reproduceable for me whenever i have large scale ground combat
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well     - current campaign is 463 years but happened as early as 100 years.

The ground log is an issue I also have reported and was leading to insane amount of mb weight of the database which increases the save and loading time.

The out of memory does not surprise me also considering we are running a 32bit version and Steve hasn't release a 64 yet.

That may also fix the issue just for a bit but I really think the entry logs of ground combat should get expunged every contruction cycle.

One thing I found bizarre is that deleting logs from the database is not reducing the save file size - its just hovering at 150mb. Whats even weirder is that the DB size is also not increasing as I play further into the game/ I also deleted other space related combat logs on top of GC logs. What is taking up all that space?

[db48x]

One thing I found bizarre is that deleting logs from the database is not reducing the save file size - its just hovering at 150mb. Whats even weirder is that the DB size is also not increasing as I play further into the game/ I also deleted other space related combat logs on top of GC logs. What is taking up all that space?

Deleting rows from a table in an sqlite database does not immediately make the file smaller. The file is divided into 4-kilobyte pages, and when a page is emptied it is simply reused for future writes. You can use the VACUUM command to remove empty pages from the file.

[Droll]

One thing I found bizarre is that deleting logs from the database is not reducing the save file size - its just hovering at 150mb. Whats even weirder is that the DB size is also not increasing as I play further into the game/ I also deleted other space related combat logs on top of GC logs. What is taking up all that space?

Deleting rows from a table in an sqlite database does not immediately make the file smaller. The file is divided into 4-kilobyte pages, and when a page is emptied it is simply reused for future writes. You can use the VACUUM command to remove empty pages from the file.

Thanks - that took it from 150 mb to 90 mb

[Froggiest1982]

from 230mb to 22mb