Performance problem, running out of mem changing properties of a large no of objects

Rhino Rhino for Mac
1

Rhino 5C256 is having grave problems changing object properties of a large number of objects.
Steps:

  1. select all objects on layer (of a 2D imported .dwg) containing about 60000 objects
  2. open object properties panel
  3. change “Display Color:” to “By Layer”
  4. leave computer open to work on it for 10 hours
  5. come back to see your mac having run out of application memory

Is there a way to do this in a way that would work for large numbers of objects? I need to do this.

2

Out of interest, what Mac are you using and how much memory do you have at the moment?

3

Well that’s of course a good part of a bug report too. I’m on a MacBook Pro (Retina, 15-inch, Late 2013) with a 2,6 GHz Intel Core i7, 16 GB 1600 MHz DDR3 and a 1 TB SSD. OS is version 10.11.6 (15G1004).

4

On my Windows machine, with 62,500 squares, the change is virtually instantaneous. (I have a pretty decent desktop workstation). With 62,500 cubes, it takes about a second.

On my Mac - a mid 2010 MBP with 8 Gigs of RAM, it does appear to beachball rather badly… Not going to let it run ten hours of course, but there is obviously a problem… ISTR that this has been reported before with large numbers of objects and obj properties…

–Mitch

edit: @mku - try the attached script. Copy it to your desktop and then type _RunPythonScript, browse to the script file on your desktop and run it. Should take a second or two to execute… @dan Definitely something wrong with Properties in this regard…

ChangeObjColorToByLayer.py (203 Bytes)

5

@Helvetosaur, thanks a million! The script is just what I suspected I should be able to do. Thanks also for reassuring that the behaviour really is a bug. I hope some coders are already hard at work fixing it…?

6

Yeah, this seems odd. Thanks for the head’s up. I’ll dig into this more.