Qutting the running project also quits the editor

[Coder2195Text]

Godot version

v4.0rc1

System information

Ubuntu 22.04 Running on Vulkan Mesa Intel® UHD Graphics 620 (WHL GT2)

Issue description

I do not know how to describe in words, so watch the video

As for the end part when I say "Godot has crashed" it didn't crash, its the quit game button quit the editor along with it

Screencast.from.02-09-2023.08.49.24.PM.webm

Steps to reproduce

Use the minial reproduction project below.

Extract it.

DONT OPEN THE PROJECT JUST YET IN GODOT.

Run cargo build in the root directory of the extracted project

After finish, open the project in Godot.

If there are no scenes open, open scenes/Scene1.tscn

Your screen should look like this, a result of the scenes/Scene1.tscn redirecting to scenes/Scene2.tscn

Now this issue is focused upon the quitting of the glitch creates, so press the button

Your editor should quit

Minimal reproduction project

minimal.zip

[Calinou]

@Coder2195Text Please upload a minimal reproduction project to make this easier to troubleshoot.

Can you reproduce this on 3.5.1 using the same code?

[akien-mga]

Sounds like your game's main scene has a @tool script which creates an overlay, and quitting it quits the editor.

[Coder2195Text]

minimal.zip

Use the minial reproduction project above.

Extract it.

DONT OPEN THE PROJECT JUST YET IN GODOT.

Run cargo build in the root directory of the extracted project

After finish, open the project in Godot.

If there are no scenes open, open scenes/Scene1.tscn

Your screen should look like this, a result of the scenes/Scene1.tscn redirecting to scenes/Scene2.tscn

Now this issue is focused upon this vulnerability to quitting, in which I happened to find out through issue #73064 creates, so press the button to experience the quitting part.

Your editor should quit

[bluenote10]

Sounds like your game's main scene has a @tool script which creates an overlay, and quitting it quits the editor.

@akien-mga The example uses gdextension, where unfortunately everything has tool semantics now. I'm frequently crashing the editor as a result of this as well. The example just does a get_tree().quit(0) which apparently, when executed from a gdextension, terminates the entire scene tree of the editor.

This is basically another manifestation of #54999 and the more I think about it, the more I believe that gdextension nodes should not run in the editor by default, and opt-in to "tool semantics" only if necessary.

@Coder2195Text As an ugly work-around probably can litter your code checks on is_editor_hint to manually opt-out from executing "dangerous code" in the editor 😕

[Coder2195Text]

Sounds like your game's main scene has a @tool script which creates an overlay, and quitting it quits the editor.

@akien-mga The example uses gdextension, where unfortunately everything has tool semantics now. I'm constantly crashing the editor as a result of this as well. The example just does a get_tree().quit(0) which apparently, when executed from a gdextension, terminates the entire scene tree of the editor.

This is basically another manifestation of #54999 and the more I think about it, the more I believe that gdextension nodes should not run in the editor by default, and opt-in to "tool semantics" only if necessary.

@Coder2195Text As an ugly work-around probably can litter your code checks on is_editor_hint to manually opt-out from executing "dangerous code" in the editor confused

I already found it all out, I opened a separate issue for the overlay thingy (issue #73064)

And this issue is one of the glitches that come of the overlay

[Calinou]

Duplicate of #54999 (same cause).