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

errors at godot 3.0 startup #7888

Closed
Ahmed0425 opened this issue Feb 25, 2017 · 9 comments
Closed

errors at godot 3.0 startup #7888

Ahmed0425 opened this issue Feb 25, 2017 · 9 comments

Comments

@Ahmed0425
Copy link

getting these errors at the startup of godot (project manager starts correctly)

ERROR: There are still MemoryPool allocs in use at exit!
At: core/dvector.cpp:71
ERROR: get_parent_class: Condition ' !ti ' is true. returned: StringName()
At: core/class_db.cpp:279
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
At: tools/editor/editor_data.cpp:628
ERROR: get_parent_class: Condition ' !ti ' is true. returned: StringName()
At: core/class_db.cpp:279
ERROR: In Object of type 'VBoxContainer': Attempt to connect nonexistent signal 'button_selected' to method 'CanvasItemEditorViewport._on_select_type'
At: core/object.cpp:1502
ERROR: environment_set_tonemap: Condition ' !env ' is true.
At: drivers/gles3/rasterizer_scene_gles3.cpp:954
ERROR: get_parent_class: Condition ' !ti ' is true. returned: StringName()
At: core/class_db.cpp:279

my opengl version is 3.3 pc specifications are (taken by CPU-Z & GPU-Z)
http://gpuz.techpowerup.com/17/02/25/z7a.png
DESKTOP-PV7L1CS.txt

@bojidar-bg
Copy link
Contributor

Can you retest with current master?

@karroffel
Copy link
Contributor

possibly related to #8105

@Ahmed0425
Copy link
Author

@karroffel Exactly
@bojidar-bg Tested and didn't work

@jedStevens
Copy link

Are you opening a previously created scenes with 3D meshes? I found my similar GL errors went away after creating a new project.

@Ahmed0425
Copy link
Author

@jedStevens No ... I open a blank project

@Keetz
Copy link
Contributor

Keetz commented Apr 6, 2017

Experiencing the same on Windows 8.1

ERROR: There are still MemoryPool allocs in use at exit!
At: core/dvector.cpp:68

At line 68 instead of 71 though

EDIT
Just a little funny side node, and possible workaround.

image

This is how godot looks when starting a project and those errors appear.
If the "maximize" icon is clicked so the godot window goes away from fullscren, godot appears again and works.

@akien-mga
Copy link
Member

A long time has passed since, so assuming fixed in 3.0 beta 2 or later. Please comment if you still reproduce the exact same errors.

@akien-mga akien-mga added the bug label Jan 4, 2018
@akien-mga akien-mga added this to the 3.0 milestone Jan 4, 2018
@Ahmed0425
Copy link
Author

No, I do not reproduce this anymore

@t-money-g
Copy link

I received this error with 3.1.1 stable branch when starting the 2d hdr example:
OpenGL ES 3.0 Renderer: GeForce GTX 1060/PCIe/SSE2
Running: C:\Godot\godot\bin\3.1.1\godot.windows.tools.64.exe --path C:/Users/tyoun/src/Learning%20Godot/godot-demo-projects/2d/hdr --remote-debug 127.0.0.1:6007 --allow_focus_steal_pid 15328 --position 420,180
OpenGL ES 3.0 Renderer: GeForce GTX 1060/PCIe/SSE2
WARNING: ObjectDB::cleanup: ObjectDB Instances still exist!
At: core\object.cpp:2095
ERROR: There are still MemoryPool allocs in use at exit!
At: core\pool_vector.cpp:70

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

No branches or pull requests

7 participants