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
Game freezes on launch on Ubuntu #17391
Comments
Check your GPU driver. WildfireGames claim that should be functional on that system (Ctrl-F on R6 at https://feedback.wildfiregames.com/report/opengl/feature/GL_KHR_debug) but it bases that on a very small sample pool. Note that this is OpenGL 4.3 so the driver should be 4.3-capable. |
|
You can try updating mesa - it's on 19.2.6 now. |
Some developments:
|
@dragunoff did you try launching all mods? If #17528 (comment) is the same as this issue it implies that you may be able to launch TD without problem. |
@pchote Yes, I tried all mods and got the same result. I tried your rendertests again but I'm not even getting a graphics.log anymore so the one linked above may be related to something else... Output of
|
#17603 has been merged, but keeping this open and on the milestone until we can find a proper resolution to the issue. The current plan (discussed in IRC) is to release the first playtest as-is, but toggle |
I can confirm the crash and complete desktopfreeze on my system. Systemspecs: |
@ripper81 can you please post the output of |
|
I can confirm the game freeze. By adding Graphics.DisableGLDebugMessageCallback=true I can start the game. Systemspecs: $> glxinfo -B OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.8 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.2.8 |
Issue Summary
Building and launching the bleed branch on Ubuntu causes the game to freeze - nothing is rendered and the window becomes unresponsive. After terminating the program the crash window appears but no logs are created.
System Information
Bisecting reveals 36c48e1 as the culprit. So this has got something to do with "Using a glDebugMessageCallback instead of glGetError". What can I do to help track down the problem?
Ping @vesuvian
The text was updated successfully, but these errors were encountered: