#The engine stops calling _can_drop_data, forcing me to restart the editor

7 messages · Page 1 of 1 (latest)

mint meadow
#

I'm having an odd issue so intermittently that I don't know how to replicate it consistently: drag and drop stops working, as in it stops calling _can_drop_data on any of my controls at all. Weirdly, it will let me start a drag, and calls _drag_data, but then no matter where I put it it will always count the drag as unsuccessful (triggering _notification)

I can't figure out the cause, sometimes it seems to happen just from running around in-game doing nothing, but I can restart the game instance and the issue persists. The only way to fix it is to literally restart the editor itself, and then the issue vanishes until it reappears later.

I don't know where to begin with fixing this. It seems like it might be an engine bug, but I wanted to know if anyone has any thoughts on how to narrow down the cause of this issue before I make a uselessly vague bug report. Do I need to compile the engine with debug symbols or something?

mint meadow
#

OKAY

#

I managed to catch something while running Godot from a terminal

#
ERROR: 3 RID allocations of type 'P11GodotArea2D' were leaked at exit.
ERROR: 1 RID allocations of type 'P12GodotShape2D' were leaked at exit.
ERROR: 1 shaders of type CanvasShaderRD were never freed
   at: ~ShaderRD (servers/rendering/renderer_rd/shader_rd.cpp:841)
ERROR: 1 RID allocations of type 'N10RendererRD15MaterialStorage8MaterialE' were leaked at exit.
ERROR: 1 RID allocations of type 'N10RendererRD15MaterialStorage6ShaderE' were leaked at exit.
ERROR: 2 RID allocations of type 'N10RendererRD14TextureStorage7TextureE' were leaked at exit.
ERROR: 21 RID allocations of type 'N18RendererCanvasCull4ItemE' were leaked at exit.
WARNING: 4 RIDs of type "Texture" were leaked.
     at: finalize (drivers/vulkan/rendering_device_vulkan.cpp:9626)
#

I have no idea what this means but it happened on closing the game immediately after issue occurred

#

This error message doesn't occur normally

#

Okay, the error occurred again, this time without that error message and also I didn't need to restart the editor, it just went away on restarting the game