Author Topic: CTD on autosave  (Read 1853 times)

Offline Procyon

  • Newbie Mark II
  • *
  • Posts: 10
CTD on autosave
« on: December 22, 2014, 06:54:53 pm »
I've yet to figure out why, but recently, AI War has managed to crash whenever it attempts an autosave, straight to the desktop. Enclosed are the logs related to one of the days that this occurred.

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: CTD on autosave
« Reply #1 on: December 22, 2014, 07:41:24 pm »
Hey there, most likely you need to turn off the option in settings that tries to submit high scores to steam. That option specifically can cause this on some systems.

Hope that helps!
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline Procyon

  • Newbie Mark II
  • *
  • Posts: 10
Re: CTD on autosave
« Reply #2 on: December 22, 2014, 07:46:40 pm »
Oh, I should have specified that this isn't the version that uses Steam. As such, that might be why I can't find said option in the menu.

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: CTD on autosave
« Reply #3 on: December 22, 2014, 10:12:26 pm »
Hmm, okay.  Well, this does jump out at me then, although it's often wildly inaccurate:

Quote
56% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [69 MB free].
Write to location 00000008 caused an access violation.

Sometimes not having a pagefile set up on your machine can cause issues, but usually not at 56% ram utilization.  I have 24gb of ram and no pagefile and no problems.  But when I had 6gb of ram and no pagefile it would start giving me trouble at about 80% ram usage for the system (in a variety of programs, actually).

One of the things that is possible is that the save files are causing memory usage spikes due to your savegame just getting absolutely huge.  We try to do garbage collections right before and after that, but sometimes it kills it anyway.  It could be that you're exceeding the amount of managed memory space (about 800mb) inside the process, simply by having a massive game going.  Or it could be that you're exceeding the 32bit windows program max size (about 3gb) if you have the option selected to preload all textures.

If you hit F3 while in game, you can look at the amount of managed memory in use there while you are in your game.  If it's 500+ mb, then that might be the problem right there.

One solution might be to not compress your savegames, if that is a problem.  It will use more space on disk, but that's about it.  In order to compress your savegame, it has to first write the savegame into ram, then transcode that into a compressed format, then save that to disk, then clear both from memory.  In the Advanced tab of the settings, there is a Don't Compress Savegames option -- perhaps that will help.
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline Procyon

  • Newbie Mark II
  • *
  • Posts: 10
Re: CTD on autosave
« Reply #4 on: December 22, 2014, 10:15:02 pm »
Neat! As a recent CompSci grad, I find the details fascinating. :D

Thanks for the response, I'll try those options.

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: CTD on autosave
« Reply #5 on: December 23, 2014, 12:12:17 pm »
My pleasure!
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!