Memory Issue Causing Crash

[ethanr]

I have a fairly new PC with many multiples the system requirements for the game. I have no idea why there would be a memory issue.

Before the safeguard was put in in the last patch, the game would just crash. Now, it autosaves and exits.

There is no rhyme or reason as to when it happens. Sometimes during the offseason, sometimes in modern 2D view play-by-play, sometimes when putting players on the trade block, sometimes during Rule 5. Sometimes after hours of play, sometimes after a few minutes.

League file uploaded to the ftp, titled "Memory Issues.zip".

Thanks!

Originally Posted by ethanr

I have a fairly new PC with many multiples the system requirements for the game. I have no idea why there would be a memory issue.

Before the safeguard was put in in the last patch, the game would just crash. Now, it autosaves and exits.

There is no rhyme or reason as to when it happens. Sometimes during the offseason, sometimes in modern 2D view play-by-play, sometimes when putting players on the trade block, sometimes during Rule 5. Sometimes after hours of play, sometimes after a few minutes.

League file uploaded to the ftp, titled "Memory Issues.zip".

Thanks!

Grabbing your save file. You mention the offseason and Rule 5. Do you reckon I can trigger it with auto play?

If I'm not mistaken, you have the baseball cards active in that save right? Unfortunately, they do eat up a lot of RAM. Loading up your game, the application immediately takes close to 3G. Unfortunately - and this is irregardless of how much RAM you have on your CPU - 32bit applications are locked at a maximum of 4G usage and nothing can be done about that number with that architecture. With fragmentation, that number can actually be closer to 3.5G. I've looked at the increasing RAM and it does seem to rise quite a bit on each card creation and quickly reaches the dander zone of 3.5-4G ram usage where new allocations will start to fail. We decided to protect progress by auto saving and closing (allowing to reload with an unfragmented clean slate of memory) before it was lost then allow memory corruption from failed allocations and crashes that could do a lot of damage to the files. I would recommend that as a power user you consider disabling some RAM intensive features to attempt to stay under the 3G to try to get many more seasons in. We'll look into what we can do to ease things, and find alternate solutions, but there are limitations to what we can do yet still try to offer as many features as we want to offer.

[ethanr]

Originally Posted by Chris Ferrario

If I'm not mistaken, you have the baseball cards active in that save right? Unfortunately, they do eat up a lot of RAM. Loading up your game, the application immediately takes close to 3G. Unfortunately - and this is irregardless of how much RAM you have on your CPU - 32bit applications are locked at a maximum of 4G usage and nothing can be done about that number with that architecture. With fragmentation, that number can actually be closer to 3.5G. I've looked at the increasing RAM and it does seem to rise quite a bit on each card creation and quickly reaches the dander zone of 3.5-4G ram usage where new allocations will start to fail. We decided to protect progress by auto saving and closing (allowing to reload with an unfragmented clean slate of memory) before it was lost then allow memory corruption from failed allocations and crashes that could do a lot of damage to the files. I would recommend that as a power user you consider disabling some RAM intensive features to attempt to stay under the 3G to try to get many more seasons in. We'll look into what we can do to ease things, and find alternate solutions, but there are limitations to what we can do yet still try to offer as many features as we want to offer.

I appreciate the timely response and the feedback. I rarely even look at the baseball cards, so I can disable that feature. I understand the balance you're talking about between features and limitations. You guys have my support. Thank you!