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
OS/device including version:
Windows 10 Home, Version 1809, OS Build 17763.914
Issue description:
If run normally the game will not crash, but stepping through the code with the GDScript debugger causes the debugger to crash the instant a doubly linked list is made using a Dictionary. The moment the list is linked both forwards and backwards, the debugger crashes.
Steps to reproduce:
Use a dictionary with "next" and "previous" keys as a structure for a doubly linked list.
Use a loop inside _ready() to create the doubly linked list.
Run the game and it will not crash.
Step through code with the debugger and it will crash on the second loop when "previous" is assigned to the first list item.
A doubly-linked list in GDScript calls for reference cycles (as in a graph). Item 1 references item 0, item 0 references item 1. The debugger may be fixed to not crash in this case, but you still have a memory leak problem.
To workaround this:
Change your list items to derive from Object (if they don't already), but take care freeing them after use
Or have your items in a separate array, and store indexes to that array in your list items
Godot version:
v3.1.1.stable.official
OS/device including version:
Windows 10 Home, Version 1809, OS Build 17763.914
Issue description:
If run normally the game will not crash, but stepping through the code with the GDScript debugger causes the debugger to crash the instant a doubly linked list is made using a Dictionary. The moment the list is linked both forwards and backwards, the debugger crashes.
Steps to reproduce:
Minimal reproduction project:
Doubly Linked.zip
The text was updated successfully, but these errors were encountered: