I didn’t make any changes in the project settings or something, but I did change some GDScript. After I did that, every time I open a different scene in the scene dock the Engine crashes. This right here is the backtrace:
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.2.stable.official (15073afe3856abd2aa1622492fe50026c7d63dc1)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x7fbfbac9c050] (??:0)
[2] godot::SceneTree::get_edited_scene_root() const (??:0)
[3] OrchestratorMainView::_on_scene_tab_changed(int) (??:0)
[4] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x3b38b48] (??:0)
[5] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x3ba02d0] (??:0)
[6] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x15aca36] (??:0)
[7] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x3ba02d0] (??:0)
[8] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x2391ef6] (??:0)
[9] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x23a255d] (??:0)
[10] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x20cdda5] (??:0)
[11] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x2126a2e] (??:0)
[12] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x212884e] (??:0)
[13] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x21376e9] (??:0)
[14] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x420ac0e] (??:0)
[15] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x493d3f] (??:0)
[16] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x3963f82] (??:0)
[17] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x396575f] (??:0)
[18] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x497bfd] (??:0)
[19] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x41e8a6] (??:0)
[20] /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7fbfbac8724a] (??:0)
[21] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fbfbac87305] (??:0)
[22] /home/marty/Schreibtisch/Godot_v4.2.2-stable_linux.x86_64() [0x42a59a] (??:0)
-- END OF BACKTRACE --
================================================================
I can also share the project files if that would be useful (I plan on open-sourcing it either way). I am using Debain 12 (GNU/Linux) using Gnome. In the backtrace I used Godot 4.2.2, but until just now where the crashes set in, I was using the latest Godot 4.3 dev6 build. So these crashes don’t occur because of the dev builds.
SOLUTION: Turns out this problem happened because I was using the Orchestrator plugin (GDExtention plugin, pretty cool visual scripting language). This was causing the crashes. After removing the folder for the orchestrator, that fixed the problem.
Signal 11 is a segmentation fault on Linux systems. It means your program (Godot) is trying to access memory that doesn’t belong to it. If it showed up in Dev6, it would most certainly help to file a formal bug report.
That may also help you narrow the issue down on your end, but this is part of why you never want to risk using a dev build on a real project. They just aren’t done yet.
Sorry I can’t be much help but if you revert your recent changes does it still crash?
Yes it does still crash after that. I have even completely removed the script I have been working on and it did not change anything. Thank you for trying to help me though!
If removing the script doesn’t stop it crashing then perhaps it was never the script’s fault. Might be worth seeing if others have had your issue: https://github.com/godotengine/godot/issues
I don’t think this community will be of much help with a Segmentation Fault.
Ideally you would report this along with a minimal project where it happens. In your case, since you don’t really know how it started, stripping back as much as you can from your project and uploading that would probably be helpful for the devs.
In the report you should be very clear which version you were using when it happened the first time (4.3 dev6?), and which other version also keeps crashing after this (4.2.2?).
