Version

• Phaser Version: v3.85.0

• Operating system: Windows 11 Pro 22631.4460

• Browser: Chrome

Description

I noticed that my phaser game was crashing when I went away from it for a while and came back to the tab.

At https://ubershmekel.github.io/bell-curve-balls/ there are a lot of balls, so the simulation step is a bit heavier than usual.

Example Test Code

• https://phaser.io/examples/v3.85.0/physics/matterjs/view/pachinko?display_mode=full_screen works more slowly. You have to create a few balls then be away from the tab for 20 minutes before you see the delays. Code at https://phaser.io/examples/v3.85.0/physics/matterjs/view/pachinko
• https://ubershmekel.github.io/bell-curve-balls/ works pretty quickly, just click it once to let the balls roll, then go to another tab and wait 1-2 minutes and when you come back to this tab it will be multiple seconds until you can play again. Code at https://github.com/ubershmekel/bell-curve-balls

Additional Information

Options I see:

• Engine.update should be called while in the background
• Do not call Engine.update to catch up when the tab becomes active, just resume the game from where it was when the tab became inactive.
• Create some "simulation is catching up spinner UI" for when the tab becomes active again.

The relevant code is at:

• This is the function that gets called multiple times during the performance freeze:

  phaser/src/physics/matter-js/lib/core/Engine.js

  Line 84 in 97e3e67

  Engine.update = function(engine, delta) {

• This is the function that takes a ton of time to complete because of all the Engine.update calls:

  phaser/src/physics/matter-js/World.js

  Line 1268 in 97e3e67

  Engine.update(engine, engineDelta);