Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: cleanup: There are still MemoryPool allocs in use at exit! #275

Open
xDGameStudios opened this issue Apr 18, 2019 · 1 comment
Open

Comments

@xDGameStudios
Copy link

xDGameStudios commented Apr 18, 2019

I have 2 classes in the GDNative plugin (Vertex and ListDigraph) and ListDigraph has a method add_vertex that return a Ref

Ref<Vertex> ListDigraph::add_vertex() {
	return Ref<Vertex>::__internal_constructor(Vertex::_new());
}

And is bound to the GDScript using:

register_method("add_vertex", &ListDigraph::add_vertex);

Having this code gives some silent errors:

  1. At editor start-up:
ERROR: set_path: Another resource is loaded from path: res://bin/list_digraph.gdns (possible cyclic resource inclusion)
   At: core/resource.cpp:79.
  1. At editor shut down
WARNING: cleanup: ObjectDB Instances still exist!
   At: core/object.cpp:2092.
ERROR: cleanup: There are still MemoryPool allocs in use at exit!
   At: core/pool_vector.cpp:70.

What am I doing wrong here?

@follower
Copy link

Not sure about about (1) but there were a number of bugs/situations that could lead to (2) related to e.g. passing arrays of strings from GDScript to GDNative and associated reference counting.

Issue (2) seems to be solved for me (due to a number of recent fixes) as of the commit mentioned in #417, so you might like to try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants