Yes. It shows up on that file. A new project still has the same problem.
PixelOverK.log
Godot Engine v3.5.1.stable.custom_build.a2ebb42a8 - https://godotengine.org
OpenGL ES 3.0 Renderer: Apple M2 Pro
Async. shader compilation: OFF (enabled for project, but not supported)
PixelOver v0.16-rc2 - https://pixelover.io
ERROR: Condition "_first != nullptr" is true.
at: ~List (./core/self_list.h:108) - Condition "_first != nullptr" is true.
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: cleanup (core/object.cpp:2070) - ObjectDB instances leaked at exit (run with --verbose for details).
ERROR: Resources still in use at exit (run with --verbose for details).
at: clear (core/resource.cpp:417) - Resources still in use at exit (run with --verbose for details).
ERROR: There are still MemoryPool allocs in use at exit!
at: cleanup (core/pool_vector.cpp:63) - Condition "allocs_used > 0" is true.
Pixeloverq.log
Godot Engine v3.5.1.stable.custom_build.a2ebb42a8 - https://godotengine.org
OpenGL ES 3.0 Renderer: Apple M2 Pro
Async. shader compilation: OFF (enabled for project, but not supported)
PixelOver v0.16-rc2 - https://pixelover.io
ERROR: Condition "_first != nullptr" is true.
at: ~List (./core/self_list.h:108) - Condition "_first != nullptr" is true.
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: cleanup (core/object.cpp:2070) - ObjectDB instances leaked at exit (run with --verbose for details).
ERROR: Resources still in use at exit (run with --verbose for details).
at: clear (core/resource.cpp:417) - Resources still in use at exit (run with --verbose for details).
ERROR: There are still MemoryPool allocs in use at exit!
at: cleanup (core/pool_vector.cpp:63) - Condition "allocs_used > 0" is true.