[macOS] Memory issue with 27412

[Langbart]

to consistently reproduce (1)

• add this debug message in chatHelper.js

binaries/data/mods/public/simulation/ai/petra/chatHelper.js

@@ -220 +220 @@
 
 PETRA.chatAnswerRequestDiplomacy = function(gameState, player, requestType, response, requiredTribute)
 {
+    warn(uneval(['debug', gameState, player, requestType, response, requiredTribute]))
     Engine.PostCommand(PlayerID, {
         "type": "aichat",
         "message": "/msg " + gameState.sharedScript.playersData[player].name + " " +

• start the attached replay from ticket #6654 (~2mins long)
  • commands.txt​
• the game freezes at the 97th turn
• forcefully quit the pyrogenesis app
• check activity monitor for spindump
  • For the case described above, the process is always called spindump to allocate large amounts of memory, but the process can also be called sandboxed or ReportCrash in other situations.

to consistently reproduce (2)

• pass this to the terminal and run

  pyrogenesis -replay-visual="/Users/paria\ crash"
  

• the game crashes with the following message

• check activity monitor for ReportCrash
  • same as above with spindump, if I don`t stop the process manually, the PC becomes unusable with time

bisect

• conflicting test results, could still have been due to spidermonkey
• reproducing the steps with the released A26 version did not show any problems, so the problem must be with macOS or somewhere in the development cycle of A27

[27412]

• with [27411] the game would also freeze, but once I would forcefully close pyrogenesis no extra process would be eating up my memory
  • screenshot below is from the terminal after I forcefully closed pyrogenesis on [27411]

related ticket

• #6697

related articles

• ​Why are "spindump" and "sandboxd" eating up all my CPU? (27/May/21)
• ​ReportCrash High CPU & How to Disable reportcrash in Mac OSX (28/Sep/16)
• ​What is Spindump? How to read, analysis and disable Spindump (27/Sep/18)

[Stan]

In your case it's printing the game state thousands of times that crashes the game. Is it just a way to make it faster? Can't be vulkan if it happened before. So it's Spidermonley most likely but it's probably cause we're doing something it does not like

[Langbart]

Replying to Stan‘:

In your case it's printing the game state thousands of times that crashes the game. Is it just a way to make it faster? Can't be vulkan if it happened before. So it's Spidermonley most likely but it's probably cause we're doing something it does not like

the issue is not about the lldb (ignore that), it about an external processing spinning up called spindump.

[wraitii]

@langbart -> Did this happen to you in regular play? Or just when adding some debugs?

[Stan]

spindump and sandboxd are macOS diagnostic applications apparently.

[Langbart]

Replying to wraitii:

@langbart -> Did this happen to you in regular play? Or just when adding some debugs?

• I have also noticed it in a regular game but have not found consistently reproducible steps.
  • I described some details here: Comment 1 in Ticket 6697

[Langbart]

The description was extended by another possibility to reproduce the problem consistently.

[Langbart]

• Remove bisect number
  • conflicting test results, could still have been due to spidermonkey
  • reproducing the steps with the released A26 version did not show any problems, so the problem must be with macOS or somewhere in the development cycle of A27

• lldb has been removed as it is not needed for the problem.

• Reproduction steps remain valid