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,

visit/src/avt/Pipeline/Data/avtMaterial.C

Lines 46 to 53 in b638f05

	// Jeremy Meredith, Thu Nov 4 13:36:07 PST 2004
	// 'maxMat' had a +1 from the actual highest used material number, but
	// checks for invalid numbers were using '> maxMat' instead of '>= maxMat'.
	// I change maxMat to be the actual highest used material number and
	// allocated an array of size maxMat+1 for the lut, because having maxMat
	// mean "highest used material number" seems clearer than changing the
	// invalid checks to be ">=".
	//

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...