Ghost zone generation taking a lot of resources.

[brugger1]

I had a user running VisIt and it kept running out of memory generating ghost zone information. He was doing a filled boundary plot, which required ghost zones.

Here are some annotated excerpts from the level 5 debug log.

avtLocalStructuredDomainBoundaryList::GlobalGather avtLocalStructuredDomainBoundaryList::GlobalGenerate: all lists size=4600 avtLocalStructuredDomainBoundaryList::GlobalGenerate: Domain 0 is enabled avtLocalStructuredDomainBoundaryList::GlobalGenerate: Number of known domains 4600 avtGenericDatabase::GetDomainBoundaryInformation: Global for local success GetDomainBoundaryInformation: Returning avtGenericDatabase::CommunicateGhosts: ghostType == GHOST_ZONE_DATA && HasDomainBoundaryInfo avtGenericDatabase::CommunicateGhostZonesFromDomainBoundariesFromFile: avtGenericDatabase::CommunicateGhostZonesFromDomainBoundaries:

dbi->ExchangeMaterial: FillMixedBoundaryData: SIGBUS

[markcmiller86]

So, that stuff about maximum material number I recall is here, https://github.com/visit-dav/visit/blob/b638f05efb53020ac7d4258e76b46cf13fb51092/src/avt/Pipeline/Data/avtMaterial.C#L46-L53

So, maybe just taking a quick look here to ensure the database itself isn't using some wonky material numbers like 47,232,211 and that we won't allocate an array that large here...