-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
[M1 Mac] Godot crashes on opening project with plugin installed #337
Comments
Video demonstrating installation & crashgodot-orchestrator-crash.mp4 |
Have you tried running it without the git plugin? I have now discovered that the same thing happens to me on Linux if the project has a git plugin. Without git plugin, Orchestrator plugin works fine. For some reason everything works fine for example with limboAI plugin and Orchestrator plugin, very strange. |
That's a great find @legbo, could it actually be that the git-plugin is the problem here working with GDExtensions? |
@Naros I tested Orchestrator plugin and latest Jolt extension and all is working fine together. But with random plugin from Asset library like Godot Steam not working, project (editor) started but then crashed. I tried to start plugins (Git, LimboAI, GodotSteam, Jolt) one by one without Orchestrator, and all is working fine. Console output, Orchestrator with Godot Steam:
Console output, Orchestrator with Git plugin:
|
When I try to run from the console, I get the below error. Removing the Godot git plugin (https://github.com/godotengine/godot-git-plugin) lets me boot up the project. So seems like there is some issue with the two existing at the same time as you two have stated. 😄
|
So what all these have in common is writing to the I really do not grok what causes this problem. We originally had issues with the logger on certain distributions that were using some really odd compiler switches to their distributions, such as Arch Linux, that were not including some standard C++ library functions that caused crashes. We rolled that back to pure C, but it seems to be an issue on MacOS. Overall this points to the logger, could this be a permissions issue writing to |
hi @legbo so this stack trace is interesting:
This actually doesn't indicate an issue with Orchestrator but rather an issue between Godot and GLIBC. Our bool OScriptNode::_is_in_editor()
{
return OS::get_singleton()->has_feature("editor");
} This would indicate that either (a) the OS singleton is null, which is a Godot build issue. Or it indicates that there is an issue with the underlying Godot calls internally that resolve whether the editor feature is or is not enabled. What version of GLIBC is installed? Additionally, this also smells of a GLIBC compatibility issue:
|
|
I have the same issue with Orchestrator on Linux, once both git and orchestrator are installed godot no longer starts.
GLIBC |
Describe the bug
After installing the plugin via the asset library, ensuring it is placed within the addons library, Godot can no longer load the project. Every time I select the project, the Godot engine crashes.
I do have the official Git Godot plugin (https://github.com/godotengine/godot-git-plugin) installed within the addons directory prior to installing Orchestrator.
Expected behavior
No crash occurs.
Actual behavior
Engine crashes upon loading the project.
How to Reproduce?
Using an M1 Mac, install Godot 4.2.2.
From there, using the asset library, download the latest version of Orchestrator. Make sure to uncheck the ignore root box such that it installs in the addons directory.
Select "Save and Restart" when prompted.
Observe that Godot reports it crashed. On future loading, the project selection dialog is presented, and selecting the project will crash the engine.
Godot full version
v4.2.2.stable.official [15073afe3]
Orchestrator version
2.0.1:
Additional information
Using an M1 Mac Mini with MacOS Sonoma 14.4.1.
The text was updated successfully, but these errors were encountered: