You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The editor crashes on startup while DocTools try to generate information about a property inside custom GDExtension class (if I haven't misinterpreted the backtrace). If the project is started explicitly (with the --path option) then everything works perfectly well and gdscript interprets the property.
The weirdest part is that this very property was handled fine previously. But after I made this GDExtension dependent on another one, it started crashing, and commenting out dependent code did not help.
Steps to reproduce
A simple GraphEdit property added to a godot::Object-derived class that's registered with ClassDB.
voidGenerator::_bind_methods()
{
godot::ClassDB::bind_method(godot::D_METHOD( "set_graph", "graph"), &Generator::set_graph);
godot::ClassDB::bind_method(godot::D_METHOD( "get_graph"), &Generator::get_graph);
//ADD_PROPERTY macro is the problem, setget methods work fine on their own and cause no editor crashesADD_PROPERTY(godot::PropertyInfo(godot::Variant::OBJECT, "graph", godot::PROPERTY_HINT_NODE_TYPE, "GraphEdit"), "set_graph", "get_graph");
}
Minimal reproduction project (MRP)
Verbose log of an appropriate version with the debug symbols enabled.
Adding custom classes as member objects to any other custom class crashes the editor on startup. This only happens in the GDExtension library that depends on another, even if the member is defined in the same extension.
Tested versions
v4.2.1.stable.official
System information
Godot v4.2.1.stable - Debian GNU/Linux 12 (bookworm) 12 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) () - AMD Ryzen 5 3600 6-Core Processor (12 Threads)
Issue description
The editor crashes on startup while DocTools try to generate information about a property inside custom GDExtension class (if I haven't misinterpreted the backtrace). If the project is started explicitly (with the --path option) then everything works perfectly well and gdscript interprets the property.
The weirdest part is that this very property was handled fine previously. But after I made this GDExtension dependent on another one, it started crashing, and commenting out dependent code did not help.
Steps to reproduce
A simple GraphEdit property added to a godot::Object-derived class that's registered with ClassDB.
Minimal reproduction project (MRP)
Verbose log of an appropriate version with the debug symbols enabled.
The text was updated successfully, but these errors were encountered: