this post was submitted on 12 May 2024
23 points (100.0% liked)

Godot

6007 readers
13 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
Feyter@programming.dev
23
Godot now crashes once I open another scene dock (lemmy.blahaj.zone)
submitted 7 months ago by Smorty@lemmy.blahaj.zone to c/godot@programming.dev
6 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] BoastfulDaedra@lemmynsfw.com 5 points 7 months ago

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.