forrtl: severe (174): SIGSEGV, segmentation fault occurred

[ycyeongi]

Your name

chaeyeong

Your affiliation

PNU

Please provide a clear and concise description of your question or discussion topic.

I am using GEOSChem version 13.3.0 and I ran the model with East Asia as the domain at 4x5 resolution. I got the following error. What is the problem?

********************************************
* B e g i n   T i m e   S t e p p i n g !! *
********************************************

---> DATE: 2020/01/26  UTC: 00:00  X-HRS:      0.000000
     ### MAIN: a SET_CURRENT_TIME
 HEMCO already called for this timestep. Returning.
     ### MAIN: a HEMCO PHASE 1
     ### MAIN: a INTERP, etc
     ### MAIN: Setting PBL CH4 conc
     ### Species Unit Conversion: kg/kg dry -> v/v dry ###
     ### Species Unit Conversion: v/v dry -> kg/kg dry ###
===============================================================================
TPCORE_FVDAS (based on GMI) Tracer Transport Module successfully initialized
===============================================================================
     ### MAIN: a DO_TRANSPORT
     ### MAIN: a SETUP_WETSCAV
     ### MAIN: a COMPUTE_PBL_HEIGHT
     ### DO_DRYDEP: after dry dep
     ### MAIN: a DO_DRYDEP
HEMCO (VOLCANO): Opening /home/data/ExtData/HEMCO/VOLCANO/v2024-03/2020/01/so2_volcanic_emissions_Carns.20200126.rc
 Filled restart variable with default 2D field: DEP_RESERVOIR
 No restart field found: GWET_PREV
 No restart field found: PFACTOR
 No restart field found: DRYPERIOD
 No restart field found: LAI_PREVDAY
 Filled restart variable with default scalar: T_PREVDAY
 Filled restart variable with default scalar: T_DAVG
 Filled restart variable with default scalar: PARDR_DAVG
 Filled restart variable with default scalar: PARDF_DAVG
--- Initialize surface boundary conditions from input file ---
--> CCl4 will use prescribed surface boundary conditions from field SfcVMR_CCl4
--> CFC11 will use prescribed surface boundary conditions from field SfcVMR_CFC11
--> CFC113 will use prescribed surface boundary conditions from field SfcVMR_CFC113
--> CFC114 will use prescribed surface boundary conditions from field SfcVMR_CFC114
--> CFC115 will use prescribed surface boundary conditions from field SfcVMR_CFC115
--> CFC12 will use prescribed surface boundary conditions from field SfcVMR_CFC12
--> CH2Cl2 will use prescribed surface boundary conditions from field SfcVMR_CH2Cl2
--> CH3Br will use prescribed surface boundary conditions from field SfcVMR_CH3Br
--> CH3CCl3 will use prescribed surface boundary conditions from field SfcVMR_CH3CCl3
--> CH3Cl will use prescribed surface boundary conditions from field SfcVMR_CH3Cl
--> CHCl3 will use prescribed surface boundary conditions from field SfcVMR_CHCl3
--> H1211 will use prescribed surface boundary conditions from field SfcVMR_H1211
--> H1301 will use prescribed surface boundary conditions from field SfcVMR_H1301
--> H2402 will use prescribed surface boundary conditions from field SfcVMR_H2402
--> HCFC141b will use prescribed surface boundary conditions from field SfcVMR_HCFC141b
--> HCFC142b will use prescribed surface boundary conditions from field SfcVMR_HCFC142b
--> HCFC22 will use prescribed surface boundary conditions from field SfcVMR_HCFC22
--> N2O will use prescribed surface boundary conditions from field SfcVMR_N2O
--> OCS will use prescribed surface boundary conditions from field SfcVMR_OCS
--> H2 will use prescribed surface boundary conditions from field SfcVMR_H2
--- Finished initializing surface boundary conditions ---
     ### MAIN: a HEMCO PHASE 2
     ### Species Unit Conversion: kg/kg dry -> v/v dry ###
     ### Species Unit Conversion: v/v dry -> kg/kg dry ###
     ### MAIN: a Compute_Sflx_For_Vdiff
     ### Species Unit Conversion: kg/kg dry -> v/v dry ###
forrtl: severe (174): SIGSEGV, segmentation fault occurred
forrtl: severe (174): SIGSEGV, segmentation fault occurred

[yantosca]

Thanks for writing @ycyeongi. A segmentation fault is when the code tries to access a memory location that is invalid. It could indicate that your run has used up all of the available memory. We do have some documentation about seg faults here:

• https://geos-chem.readthedocs.io/en/latest/geos-chem-shared-docs/supplemental-guides/error-guide.html#segmentation-faults-and-similar-errors
• https://geos-chem.readthedocs.io/en/latest/geos-chem-shared-docs/supplemental-guides/debug-guide.html