Closed ananddoss2004 closed 2 years ago
Quick notes:
Courant No = 0 probably because the initial U field is set to 0.0...
This:
ZN4Foam12compressible56turbulentTemperatureCoupledBaffleMixedFvPatchScalarField12updateCoeffsEv ...
ZN4Foam17mixedFvPatchFieldIdE8evaluateENS_8UPstream10commsTypesE [0x6b6980c2+0x22]
ZN4Foam29mixedEnergyFvPatchScalarField12updateCoeffsEv [0x6a30bd43+0xd3]
mixedEnergy
.More specifically, sigSegV usually means that a bad memory access was attempted, resulting in the application crashing. Said crash seems to have been due to something going wrong during mapping between patches....
ZN4Foam15mappedPatchBase9facePointERKNS_8polyMeshEiNS1_17cellDecompositionE [0x632cfdee+0x28e]
ZNK4Foam15mappedPatchBase10facePointsERKNS_9polyPatchE [0x632d01db+0x9b]
ZNK4Foam15mappedPatchBase11calcMappingEv [0x632d488f+0x7f]
ZNK4Foam15mappedPatchBase10distributeIdEEvRNS_4ListIT_EE [0x6b751d15+0x1c5]
ZN4Foam12compressible56turbulentTemperatureCoupledBaffleMixedFvPatchScalarField12updateCoeffsEv [0x6b6486b9+0x2a 9]
The words mapped
and turbulentTemperatureCoupledBaffleMixed
appear in there, which refer to such a mapped patch between regions...
I did not look into the case, since it would take considerable time to do so.
Issue Resolved.
Hello Brunos,
For the first time, I am experiencing SigSegV handler error as follows,
I believe its signal segmentation error and something to do with temperature boundary condition. I have attached the boundary condition files. Please help me what cause this error ?
Also courant number for air is zero, how? Case.zip