8000 Crash when adding a custom version of Godot · Issue #99 · eumario/godot-manager · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Crash when adding a custom version of Godot #99

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.

Sign up for GitHub

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

Jump to bottom
Open
deevus opened this issue Jul 11, 2024 · 1 comment
Open

Crash when adding a custom version of Godot #99

deevus opened this issue Jul 11, 2024 · 1 comment

Comments

@deevus
Copy link
deevus commented Jul 11, 2024

Describe the bug
When trying to add a custom version, the manager window closes without any message. The custom version is not saved.

To Reproduce
Steps to reproduce the behavior:

  1. Click "Add Custom Version"
  2. Enter "Test" for Godot Engine Tag
  3. Browse and select any executable
  4. Click Add

Expected behavior
The custom version is added.

Screenshots
image

Complete the Following:

  • OS: Windows 11
  • Version 0.2.5 and 0.2.9

Additional context
@deevus
Copy link
Author
deevus commented Jul 11, 2024 •
edited
Loading

Found this log
godot2024-07-11T18.35.05.log

Godot Engine v3.5.3.stable.mono.official.6c814135b - https://godotengine.org
OpenGL ES 3.0 Renderer: AMD Radeon RX 6900 XT
Async. shader compilation: OFF
 
Mono: Log file is: 'C:/Users/Simon/AppData/Roaming/Godot-Manager/mono/mono_logs/2024-07-11_18.24.27_2652.log'
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@deevus
0