SketchUp 2015 (Mac) Component panel freezing application

kado · 14 Oct 2016, 00:12

In one particular file only, whenever I attempt to open the Components panel, the app stops responding forcing me to force quit and re-open.

I've even exploded every single component in the file, saved as new file, re-opend and tried opening the Components panel with the same result.

What else can I try to recover this model?

Thanks for any advice.

Dave R · 14 Oct 2016, 00:38

Try Window>Model Info>Statistics>Purge Unused.

kado · 14 Oct 2016, 18:24

@dave r said:

Try Window>Model Info>Statistics>Purge Unused.

Thanks for the reply. Followed your suggestion with no luck.

slbaumgartner · 14 Oct 2016, 20:29

How many components are in the model or the collection you are viewing? I've seen the components window freeze SketchUp (spinning beachball of death) while generating the thumbnails for a large list of components. If I wait long enough, it eventually wakes up. Having a lot of unused components in the model aggravates this problem.

kado · 15 Oct 2016, 23:00

@slbaumgartner said:

How many components are in the model or the collection you are viewing? I've seen the components window freeze SketchUp (spinning beachball of death) while generating the thumbnails for a large list of components. If I wait long enough, it eventually wakes up. Having a lot of unused components in the model aggravates this problem.

92 components with 3,500 instances. Strange thing is, even with every single component exploded (as an experiment) the same behaviour occurs.

juju · 17 Oct 2016, 10:02

@kado said:

92 components with 3,500 instances. Strange thing is, even with every single component exploded (as an experiment) the same behaviour occurs.

in your experiment, did you remember to purge the file after exploding all of the components?

slbaumgartner · 17 Oct 2016, 12:55

I agree with Juju: with every component exploded, there should be nothing to list in the component browser and the response should be snappy - unless you are trying to browse a large collection, not the in-model collection. In the latter case it may still be so large as to bog down the browser, or a slow/lagging network connection can affect it.