File audit gives me bad news: what do I do next?

Over this last week, I’ve noticed my file taking a while to open (4 minutes for a 65MB file on a Mac Studio with M1 Max chip).

On occasion, a reboot has fixed it. Today I thought I’d try the audit command. It gave me the following result…

Document Manifest:
Texture Mapping: 130 active, 1 system.
RenderMaterial[243] name missing from document manifest.
Material: Error: differences between model table[243] and manifest information.
RenderMaterial[246] name missing from document manifest.
Material: Error: differences between model table[246] and manifest information.
RenderMaterial[247] name missing from document manifest.
Material: Error: differences between model table[247] and manifest information.
RenderMaterial[248] name missing from document manifest.

Material: Error: differences between model table[265] and manifest information.
RenderMaterial[266] name missing from document manifest.
Material: Error: differences between model table[266] and manifest information.
RenderMaterial[267] name missing from document manifest.
Material: Error: differences between model table[267] and manifest information.
Material: Error: 23 errors found. Model: 245 active, 0 deleted. Manifest: 268 active, 0 deleted.
Line Pattern: 18 active, 3 system.
Layer: 78 active, 4 deleted, 1 system.
Group: 20 active.
TextStyle: none.
Annotation Style: 20 active, 12 system.
Light: 4 active.
Hatch Pattern: 13 active, 9 system.
Block: 41 active.
Model Geometry: 1635 active.

Error: 2208 model components (4 deleted). 28 system components. 2259 manifest items

object should not be on a reference layer.
object should not be on a reference layer.
object should not be on a reference layer.
object should not be on a reference layer.
object should not be on a reference layer.
object should not be on a reference layer.
object should not be on a reference layer.
object should not be on a reference layer.
m_instance_definition_table[1]->ObjectCount() = 0.
m_instance_definition_table[12]->Object(0) should not be a reference object.
m_instance_definition_table[12]->Object(1) should not be a reference object.
m_instance_definition_table[12]->Object(2) should not be a reference object.
m_instance_definition_table[12]->Object(3) should not be a reference object.
m_instance_definition_table[12]->Object(4) should not be a reference object.
m_instance_definition_table[12]->Object(5) should not be a reference object.
m_instance_definition_table[35]->Object(0) should not be a reference object.
m_instance_definition_table[35]->Object(1) should not be a reference object.
Audit Summary:
8 object errors detected.
0 linetype table errors detected.
0 layer table errors detected.
9 block table errors detected.
0 font table errors detected.
0 annotation style table errors detected.
Table tally:
78 layers
41 instance definitions
20 annotation styles
0 fonts
4 rendering lights
18 linetypes
268 rendering materials
Object tally:
1297 normal objects
0 locked objects
44 hidden objects
0 deleted objects (in undo buffer)
107 block definition objects
0 reference normal objects
0 reference locked objects
0 reference hidden objects
187 reference block definition objects
Audit found problems.

The file, once open, behaves itself. From the looks of it, the problem is with the materials. Is it a case of purging them and recreating? Also some objects with issues. I could revert to a Time Machine backup, but since this has been developing for a week, I’m hoping I could avoid having to redo a week’s work.

I ran _Check and didn’t notice any errors mentioned. I also ran _SelBadObjects and it found one example, but deleting it didn’t change anything.

Perhaps there’s a save option or something?

I’m currently using Rhino Mac 8.15.25019.13002, 2025-01-19 on Sequoia 15.3. Both were updated in the last couple of days, so after the problem started.

Hi Ray -

Please post or upload that 3dm file so that a developer can take a closer look.
Also, please run the Rhino SystemInfo command and copy-paste the output here.
-wim

Thanks for the suggestion, but no need now. I’ve managed to get it sorted. I’ve been exporting individual layers to a new file then checking that for errors. Have narrowed it down to a few potential objects so far. Looking to be (but not conclusive yet) ones I’d scanned with iRhino about a year ago, plus some materials I can recreate.

It looks like the object errors have been there for many months, but the material issues were newer. Probably related to this issue too.

It would be nice to have an audit report list problem items with an identifier which can be searched for (or at least, the layer).

In any case, I’d be reluctant to upload this for your developers to look at. I’ve previously posted 4 bugs, going back 9 months, all still in the queue. I’d be uncomfortable bothering the already overloaded developers with my minor issues.