Build: 1.3.4 3210 Mode: Any Mode: Singleplayer SERVER NAME: (If the issue happened on a public server, please add the name here) SEED-ID: (Please always add the SEED-ID for SingleplayerSurvival games; Open the console. The Seed is noted somewhere to the "playfield loaded" dialogue) If applicable: MODIFIED PLAYFIELDS: Yes/No/DontKnow (<- YES if new planets or non-default playfields are used. Use DontKnow if you are not aware if anything has been changed) Reproducibility: Always Severity: Minor Type: Summary: Bases with very large footprint causing lag Description: Spawning, loading in, or moving around a base with a very large footprint (test base is 438m x 456m x 88m but is mostly air) on a planet causes high CPU load and warnings in the console (and log file) saying: Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = XXX)" where age is some number greater then 4 Constructors finishing jobs seems to also trigger this on the test base amongst other things. Steps to Reproduce: (steps to reproduce the issue. This is ESSENTIAL for a bugfix!) Download the attached blue print and dump it in your blueprint library. Start a new game in any game mode. IMPORTANT: You must be in a planet playfield. Space playfields do NOT seem to trigger this for some reason. Spawn in the test blueprint. Open the console. You will see a new line that will say "Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak" and a second line that says something like "Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = XXX)" where age is some number greater then 4. These line will also appear in the Client Log. Leave the playfield and then return and you should get the same log output.
Build: 1.4 .1 3260 10-20:24 Mode: survival Mode: non-dedicated server - co-op SERVER NAME: SEED-ID: If applicable: MODIFIED PLAYFIELDS: scenario Reproducibility: Always Severity: Major Type: code error - locks up Summary: ship teleports after entering planet and exiting ship. Description: Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak (Filename: Line: 555) Steps to Reproduce: Throws errors to my log, and lags the game. If this is from my scenario, can you please point me in the right direction to fix it? Screenshots, Crash Logs, any other Relevant Information or Download links:
Build: 1.4.1 3260 10-23:17 Mode: Survival Mode: Coop Reproducibility: Always Severity: Major Type: Global MODIFIED PLAYFIELDS: No, just some item changes. Summary: My game stutters a bit and the log is filling up Description: Looking in the console, I'm seeing a lot of messages after this morning's update. It seemed to work fine yesterday. 10-22:45:25.983 17_45 -LOG- INFO: Uptime=01h51m mem=674MB fps=20.0 playfield=Aneis plys=2 mobs=23/155 structs=4 devices=428 chunks=815 pf-index=0 ticks=134628 10-22:46:26.061 17_46 -LOG- INFO: Uptime=01h52m mem=669MB fps=20.0 playfield=Aneis plys=2 mobs=23/155 structs=4 devices=429 chunks=815 pf-index=0 ticks=135829 10-22:46:27.862 17_46 -ERR- Cancelling O2 calculation as it took longer than 120s! struct id=1699 10-22:46:27.912 17_46 -ERR- Calling RecalcInsideOutside() while a calculation is still active! entity='Base (BA)', id=1699, cIdx=4 Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 7) (Filename: Line: 311) Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak (Filename: Line: 555) Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 8) (Filename: Line: 311) Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak (Filename: Line: 555) What line is it referring to? Something in the Config file or a line of code? SIDE NOTE: Game hasn't crashed but I'm concerned. We started over with a new game. I thought it might be old playfields data so I cleared the playfields from my scenario. All that's left are a few config files, but it's still throwing errors. Logs included. EDIT: I've been pulling my hair out all morning on this. I finally removed all of the config files from my scenario and I still have this issue on my saved game. I haven't a clue.
