[POSSIBLE BUG?] getAvailableDisplayModes() on cloned displays

[ronnocerman]

I have my monitor cloned with my TV. When I call getAvailableDisplayModes on various setups, I get these results (organized by bpp and frequency for clarity, and I only included 1080p results):

Only TV connected (14 results):
1920 width 1080 height 16 bpp 23Hz
1920 width 1080 height 16 bpp 24Hz
1920 width 1080 height 16 bpp 29Hz
1920 width 1080 height 16 bpp 30Hz
1920 width 1080 height 16 bpp 50Hz
1920 width 1080 height 16 bpp 59Hz
1920 width 1080 height 16 bpp 60Hz
1920 width 1080 height 32 bpp 23Hz
1920 width 1080 height 32 bpp 24Hz
1920 width 1080 height 32 bpp 29Hz
1920 width 1080 height 32 bpp 30Hz
1920 width 1080 height 32 bpp 50Hz
1920 width 1080 height 32 bpp 59Hz
1920 width 1080 height 32 bpp 60Hz

Only Monitor (6 results):
1920 width 1080 height 32 bpp 50Hz
1920 width 1080 height 32 bpp 59Hz
1920 width 1080 height 32 bpp 60Hz
1920 width 1080 height 16 bpp 50Hz
1920 width 1080 height 16 bpp 59Hz
1920 width 1080 height 16 bpp 60Hz

Both Connected (12 results):
1920 width 1080 height 16 bpp 23Hz
1920 width 1080 height 16 bpp 24Hz
1920 width 1080 height 16 bpp 29Hz
1920 width 1080 height 16 bpp 30Hz
1920 width 1080 height 16 bpp 59Hz
1920 width 1080 height 16 bpp 60Hz
1920 width 1080 height 32 bpp 23Hz
1920 width 1080 height 32 bpp 24Hz
1920 width 1080 height 32 bpp 29Hz
1920 width 1080 height 32 bpp 30Hz
1920 width 1080 height 32 bpp 59Hz
1920 width 1080 height 32 bpp 60Hz

This causes issues because, on some of the display modes (it seems to be the display frequencies that my monitor doesn't recognize, such as 23Hz) with both of them connected, when I go into fullscreen, my computer crashes, all displays go black, and I am forced to restart (Alt+F4, Ctrl+Alt+Delete do nothing).

It seems to me that, when the displays are cloned, it should return the intersection of each display's available display modes?

It doesn't seem to crash ever if I only have my monitor connected.

Take all this with a grain of salt, as I just started using LWJGL within the past week.

Hope this helps!