GDScript 2.0: Profiling does not seems to be working

[KaruroChori]

Godot version:
Godot 4.0 bc30df8

OS/device including version:

Linux 80x86 64bit, GTX 1660 super and RTX 2060 (main one). Drivers 450.80

Issue description:
I am working in single window mode.
When I try to profile my scene the number of objects is extremely high even with an empty one (I guess this is justr the rest of the editor showing up) an draw calls are set to zero no matter how many objects with different materials I add.

Steps to reproduce:
Open any project. Run the scene and open the profiler. Add some meshes and material. Run the scene and open the profiler. Compare the results.

Minimal reproduction project:
No need for a specific project.

[Calinou]

@KaruroChori Can you (or anyone else) still reproduce this bug in the latest master branch? You can download a nightly build here.

Also, are you referring to the GDScript profiler or the visual profiler (new in 4.0)?

[KaruroChori]

Hi, it would be hard for me to test this. In the last few months I changed graphic cards as well as drivers, so I would not be able to reproduce the exact circumstances.
Your link is not working, could you provide an updated one?
If I recall correctly it should be the one shown here: https://docs.godotengine.org/en/latest/tutorials/scripting/debug/the_profiler.html

[Calinou]

@KaruroChori I fixed the link in my comment, it should work now.

[KaruroChori]

Well, I guess it is worse than last time, now I cannot even run it :(.
#54962

[Zireael07]

Note: as of alpha 1, graphics profiling seems to be working, script profiling is NOT.

[tavurth]

Damn, this was the dealbreaker for me about moving to Godot 4 already.

Is there any timeline for when this will be implemented?

[Calinou]

Damn, this was the dealbreaker for me about moving to Godot 4 already.

Is there any timeline for when this will be implemented?

We don't know why it's broken in the first place, so there is no ETA for fixing this.

[tavurth]

Actually seems to be working if you open the debug panel before the game starts.

Seems this issue is mostly that the start button is getting greyed out incorrectly, as you can see here I also cannot stop the debugger.

[Zireael07]

@tavurth What alpha version/master hash is that?

[tavurth]

@Zireael07 That's on Alpha 4

[tavurth]

After digging some more, it appears that when entering the pause state, the proflier buttons Start and Stop become greyed out, and do not properly reset their state when the game is restarted or resumed.

So entry here:

godot/editor/debugger/editor_profiler.cpp

Lines 502 to 504 in 7e5cd4b

	void EditorProfiler::set_enabled(bool p_enable) {
	activate->set_disabled(!p_enable);
	}

And issue may lie here:

godot/editor/debugger/script_editor_debugger.cpp

Lines 300 to 331 in 5c8bd6f

	void ScriptEditorDebugger::_parse_message(const String &p_msg, const Array &p_data) {
	emit_signal(SNAME("debug_data"), p_msg, p_data);
	if (p_msg == "debug_enter") {
	_put_msg("get_stack_dump", Array());
	ERR_FAIL_COND(p_data.size() != 3);
	bool can_continue = p_data[0];
	String error = p_data[1];
	bool has_stackdump = p_data[2];
	breaked = true;
	can_debug = can_continue;
	_update_buttons_state();
	_set_reason_text(error, MESSAGE_ERROR);
	emit_signal(SNAME("breaked"), true, can_continue, error, has_stackdump);
	if (is_move_to_foreground()) {
	DisplayServer::get_singleton()->window_move_to_foreground();
	}
	if (!error.is_empty()) {
	tabs->set_current_tab(0);
	}
	profiler->set_enabled(false);
	inspector->clear_cache(); // Take a chance to force remote objects update.
	} else if (p_msg == "debug_exit") {
	breaked = false;
	can_debug = false;
	_clear_execution();
	_update_buttons_state();
	_set_reason_text(TTR("Execution resumed."), MESSAGE_SUCCESS);
	emit_signal(SNAME("breaked"), false, false, "", false);
	profiler->set_enabled(true);
	profiler->disable_seeking();

More specifically this bug occurs when:

1. The game is paused with the pause button (or clicking inside profiler)
2. The game is then restarted

• Pausing and unpausing the game does not cause this issue.
• Clicking inside the profiler (pausing) and then resuming the game does not cause this problem