[BUG] Full screen crashes ugly on some resolutions

Started by jakethesnake, November 08, 2020, 09:29:04

Previous topic - Next topic


Hello again,

I'm getting core dump crashes when choosing certain screen resolutions.

I get the displaymodes:

GLFWVidMode vmode =glfwGetVideoMode(glfwGetPrimaryMonitor());

A snipped of what it returns:
[SNAKE2D] -----1920x1080x25, 8 8 8
[SNAKE2D] -----1920x1080x29, 8 8 8
[SNAKE2D] -----1920x1080x30, 8 8 8
[SNAKE2D] -----1920x1080x50, 8 8 8
[SNAKE2D] -----1920x1080x59, 8 8 8
[SNAKE2D] -----1920x1080x60, 8 8 8


I then pick one and create the window normally:

window = glfwCreateWindow(displayWidth, displayHeight, sett.getWindowName(),
					glfwGetPrimaryMonitor() : NULL, NULL);

glfwWindowHint(GLFW_REFRESH_RATE, x);

It crashes and burns and writes a core dump.

glfwWindowHint(GLFW_REFRESH_RATE, 30)
, it works, but I'm getting a notification:

	Description : Win32: Failed to set video mode: Graphics mode not supported
	Stacktrace  :

And I'm getting 60 FPS.
glfwWindowHint(GLFW_REFRESH_RATE, 60), however, crashes with core dump.

This is consistent with all the resolutions that are getting listed, save for a very few that works flawlessly.

I'm on an external display, listed as having 2560x1440x60, 8 8 8, and that's it.

The core dump:

[SNAKE2D] ---attempting resolution: 1920x1080 true 50
# A fatal error has been detected by the Java Runtime Environment:
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffdbd1051d0, pid=8716, tid=0x00000000000058c0
# JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [glfw.dll+0x51d0]
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# An error report file with more information is saved as:
# C:\Users\mail__000\Documents\syx54\Syx\hs_err_pid8716.log
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

This could probably be a driver issue, or a GLFW bug, but I'm suspecting it's your philosophy to move away from fatal java errors, so I'm wondering if that's possible?

Edit: It seems all resolutions work if I set refreshrate to 30, however, I'm always getting 60.