Hangs in Rhino 6

Hi guys,
Each time I use the test commands (Subdfrommesh) on mesh objects and then try to change the display mode Rhino hangs.
This issue I started to notice it since the first release of Rhino 6 in all display modes, in the second release I was able to view the subd objects in Rendered ( plus wireframe, and shade) display modes.
In the third release of Rhino 6, I was able to see subd objects in all display modes fine except for Arcitic and Raytraced display mode, it hangs.
In the third candidate release of Rhino 6, the issue back as it was in the first release as I am not able to view it in any display except for sure the wireframe and shade mode.
Any ideas of how to solve this?

Below is my system information:
Rhino 6 SR3 2018-3-13 (Rhino 6, 6.3.18072.11251, Git hash:master @ c0a2028629d3ed3a538f0854c8ba021ae8c678b7)

Windows 10.0 SR0.0 or greater (Physical RAM: 7.9Gb)

GeForce 840M/PCIe/SSE2 (OpenGL ver:4.6.0 NVIDIA 391.01)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 2-23-2018
Driver Version:
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 4 GB

C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands”
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\ColorPicker (336da4ab-03d3-42ca-b1fb-313bfd4c1157)\2018.2.5.819\ColorPicker.rhp “ColorPicker”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI”
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\PanelingTools (6caed836-bc06-4ebc-b1fd-e10886a0dc94)\2018.3.1.650\PanelingTools.rhp “PanelingTools”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles”
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Rhino 3DM File Version (aa091cb2-d8c0-4944-a17d-b66c80bec4ca)\\RhinoFileVersion.rhp “Rhino 3DM File Version”
C:\Program Files\Rhino 6\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper”
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars”
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\SectionTools (fbdb1d7f-8cfb-42c1-9858-87cb6315932c)\2018.1.9.1166\SectionTools.rhp “SectionTools”

That’s why they’re test commands…?

The display for SubD objects needs to be updated to work how all of the other geometry types in Rhino currently work. This is on my bug list of things to fix but it is not even close to the top of my “todo” list at the moment.

Thanks, I do already know this.
I am just wondering if they could fixed it in the previous release, why again the bug appears in their next release?

Huh…? Seems perfect!