#9014·GDevelop

Crash of the profiler due to the gameplay test

Author: BouhCreated Aug 25, 2026Updated Aug 26, 2026
Labels💥crash

Is there an existing issue for this?

Describe the bug

The gameplay test window have an crash related to the debugger. This is a reproductible crash.

Uncaught exception: Error: Impossible to call Profiler.begin() when not profiling a frame!Error: Impossible to call Profiler.begin() when not profiling a frame! at i.begin (file:///C:/Users/RTX-Bouh/AppData/Local/Temp/GDTMP--1/gameplay-test-preview/profiler.js:1:715) at u.render (file:///C:/Users/RTX-Bouh/AppData/Local/Temp/GDTMP--1/gameplay-test-preview/runtimescene.js:1:6256) at g.renderWithoutStep (file:///C:/Users/RTX-Bouh/AppData/Local/Temp/GDTMP--1/gameplay-test-preview/scenestack.js:2:1068) at file:///C:/Users/RTX-Bouh/AppData/Local/Temp/GDTMP--1/gameplay-test-preview/runtimegame.js:1:14027 at i (file:///C:/Users/RTX-Bouh/AppData/Local/Temp/GDTMP--1/gameplay-test-preview/pixi-renderers/runtimegame-pixi-renderer.js:1:11738)

Steps to reproduce

  • Run a gameplay test
  • Open the Profiler panel in the debugger and start profiling (Start profiling)

https://github.com/user-attachments/assets/755d46c0-6e28-40a9-b31e-10bd5d9b7f56

GDevelop platform

Web

GDevelop version

This version of GDevelop is: 5.6.280 (editor full version: 5.6.280-b6918151a29744bb91f89c172d21614c44fe8647, core version: 5.6.280-0)

Platform info

No response

Additional context

No response