-
-
Notifications
You must be signed in to change notification settings - Fork 635
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
Editor crashes after seconds on the native Linux version (Fedora 40 X11, works fine under Proton) #991
Comments
I'm experiencing what might be the same issue. When I start it and only add primitives like cubes, planes, point lights to the scene, the editor keeps running fine for maybe up to a minute if I'm lucky. But when I try to load a scene, load an external file like a video, or mess around in menus, it will quickly stop responding and will not recover. Running it in a terminal, then loading a scene and having it freeze, this is what it outputs:
The scene I loaded is just the startup scene saved to a new file. |
The linux version accidentially allocated the editor object (which can be 8MB) on the stack, which could lead to stack overflows. This was fixed yesterday, and while it probably doesn't fix the crashes you see, it's still a possiblity, so it would be great if you could re check with the lastest master. |
With 0.71.645 the editor doesn't start at all for me. I just built from master and the behavior is back to how I described it with 0.71.625. It seems to run fine as long as I manipulate primitives, but crashes when I try to load files, or save the scene. When saving the scene, I still get the "Scene Saved" message before it crashes. |
@Takuyax For the master build: could you compile RelWithDebInfo and run it with gdb to dump the stacktrace? The following should do it:
then, in gdb, use |
When the problem occurs in the master build, the editor doesn't close, but just hangs indefinitely, so I can't enter the bt command to get the stacktrace. After I kill the editor, it says there is no stack, but when I terminate it instead, it outputs this:
I included the output from the point when I saved the scene, which reliably causes it to freeze. Then I termintated it. I hope this is useful. |
Thank you for the stacktrace. This seems to be the same issue as in #804 (of which #855 is a duplicate), it seems to hang when waiting for fences. Could you try the following: in wiGraphicsDevice_Vulkan.cpp, around line 2951 there should be if (videoFamily == VK_QUEUE_FAMILY_IGNORED &&
queueFamily.queueFamilyProperties.queueCount > 0 &&
(queueFamily.queueFamilyProperties.queueFlags & VK_QUEUE_VIDEO_DECODE_BIT_KHR) &&
(queueFamilyVideo.videoCodecOperations & VK_VIDEO_CODEC_OPERATION_DECODE_H264_BIT_KHR)
)
{
videoFamily = i;
} Just comment out the if or just the |
@Takuyax can you try the workaround above and say if it fixes the crash? |
I commented it out, but the problem still is the same. Saving the scene still causes the problem:
|
Thanks for checking 🤔 |
Everything is in the title.
Was using the latest Steam release.
I'm using an Nvidia GPU with the latest official drivers.
The text was updated successfully, but these errors were encountered: