WARNING: cleanup: ObjectDB Instances still exist! when using GetWorld2d().DirectSpaceState

[quanixstudio]

Godot version:
v3.2.2 beta3 mono
Also tried it on v3.2.1 stable mono with the same result.

OS/device including version:
Windows10

Issue description:
When using GetWorld2d().DirectSpaceState this error is shown when quitting the application.
WARNING: cleanup: ObjectDB Instances still exist! At: core/object.cpp:2135

Steps to reproduce:

1. Generate new mono project.
2. Add a node and attach a C# script to it.
3. Save this as the main scene.
4. In the script in _PhysicsProcess store the result of GetWorld2d().DirectSpaceState to a variable.
5. Play the project and then quit.

[quanixstudio]

After some playing around I found out that it is the GetWorld2d() that causes the warning.
If I do it like this the error is not showing anymore.

using Godot;

public class Test : Node2D {
    private World2D _world;

    public override void _ExitTree() {
        _world?.Dispose();
    }

    public override void _PhysicsProcess(float delta) {
        _world = GetWorld2d();
        var spaceState = _world.DirectSpaceState;
        // Do whatever you want with the spacestate
    }
}

[madmiraal]

I'm unable to reproduce this issue. I've created a minimal reproduction project using the information provided:
39216.zip

I do not get the warning message in v3.2.1 or v3.2.2 beta 4.

@quanixstudio If you're able to provide your own minimal reproduction project that does show this warning, then please comment below.

[quanixstudio]

I downloaded your example and using it that way gave me the warning.
After that I added the Dispose and the warning was gone.

In the attached screenshot, the first run was without dispose and the second with dispose.

[madmiraal]

Looks like it may be OS specific. I'm using the x11_64 version. I see you're using the win64 version.

[pouleyKetchoupp]

Confirmed in 3.2.3 stable on Windows 10. The issue is c# specific, I can't reproduce it when using gdscript instead.

[magian1127]

3.4 There is still this problem.
windows 10 x64