V6 locking up, meshes, solved

Short version - Rhino V6 locking up solved after 597 meshes in a Worksession attachment were joined into a single mesh.

I recently have used a file with very large meshes as an attachment using Worksession. The meshes have about 7.6 million vertices and 15 million faces. I have been using Contour and drawing lines. After a few minutes Rhino would lockup with the blue circle spinning. Sometimes it would recover after several minutes, sometimes it would be locked up until I ended Rhino after twenty minutes or more. Performance monitors showed lots of disk activity and 1 of 8 CPU threads at 100%.

I then discovered that what I thought was 3 meshes was actually 599 with what should have been 1 mesh was actually 597 meshes. I joined the 597 meshes and since then the locking up has stopped.

Rhino 6 SR14 2019-3-5 (Rhino 6, 6.14.19064.4371, Git hash:master @ d340745acddd7cdc24cc31904f467821e90ed976)
License type: Commercial, build 2019-03-05
License details: Cloud Zoo. In use by: David Cockey ()

Windows 10.0 SR0.0 or greater (Physical RAM: 16Gb)
Machine name: DESKTOP-7M1R2N0

Non-hybrid graphics.
Primary display and OpenGL: AMD Radeon HD 7700 Series (AMD) Memory: 2GB, Driver date: 2-20-2019 (M-D-Y). OpenGL Ver: 4.6.13547 Compatibility Profile Context 25.20.15025.1002

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

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

Vendor Name: ATI Technologies Inc.
Render version: 4.6
Shading Language: 4.60
Driver Date: 2-20-2019
Driver Version: 25.20.15025.1002
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 2 GB

Rhino plugins
C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands” 6.14.19064.4371
C:\Program Files\Rhino 6\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 6\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 6\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 6.14.19064.4371
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 6\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Orca3D V2\Orca3D.rhp “Orca3D” 2.0.5.0
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles” 6.14.19064.4371
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 6.14.19064.4371
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”

@stevebaer - does this seem like more or less expected behavior, kind of at the limit, with very large meshes like this, or do we need to investigate further?

-Pascal

@pascal @stevebaer My reason for reporting this was the behavior was unexpected. I wonder if any of the other reported instances of locking up could be related.

  1. When 597 meshes were joined into one the number of faces and vertices were not reduced. So the number of faces and vertices by itself was not a problem.

  2. The total number of meshes was originally 599. Is this a “magic number” for the number of allowed meshes?

  3. The meshes were in an attached but not “active” file using Worksession. So I would not expect them to be saved, etc.

  4. The last time the lock up occured I was using Line independent of the meshes. It seemed like some sort of background Rhino process was causing the lock up.

Hi David - I am just taking a wild guess that with the large meshes taking a lot of resources to begin with, the per-object overhead, which can be considerable, might, just possibly, have barely taken things over some threshold into maybe paging to disk or something. But, Steve will have a better idea.

-Pascal

There is more overhead with 600 individual objects versus 1, but it shouldn’t be that noticeable. Also, there is no “magic” number where things change. I can’t really tell what happened in this situation, but it is good to hear that you were able to fix it.