Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEOS-Chem ERROR: Error allocating array ODAER! #2591

Open
Naaimaben opened this issue Nov 25, 2024 · 1 comment
Open

GEOS-Chem ERROR: Error allocating array ODAER! #2591

Naaimaben opened this issue Nov 25, 2024 · 1 comment
Assignees
Labels
category: Bug Something isn't working topic: Runtime Error Related to runtime issues (e.g. simulation stopped w/ error)

Comments

@Naaimaben
Copy link

Naaimaben commented Nov 25, 2024

I cloned geoschem (geosfp 0.25x0.3125) when I tried to run ./gcclassic i get the following error

===============================================================================
GEOS-Chem ERROR: Error allocating array ODAER!
 -> at Init_Phot_Container (in module Headers/phot_container_mod.F90)
===============================================================================
===============================================================================
GEOS-Chem ERROR: Error encountered in "Init_Phot_Container" routine!
 -> at Init_State_Chm (in module Headers/state_chm_mod.F90)
===============================================================================
===============================================================================
GEOS-Chem ERROR: Error encountered within call to "Init_State_Chm"!
 -> at GC_Init_StateObj (in GeosCore/gc_environment_mod.F90)
===============================================================================
===============================================================================
GEOS-CHEM ERROR: Error encountered in "GC_Init_StateObj!"!
STOP at  -> at GEOS-Chem (in GeosCore/main.F90)
===============================================================================
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0  0x155408afc5af in ???
#1  0x12a5866 in __hco_driver_mod_MOD_hco_final
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/HEMCO/src/Core/hco_driver_mod.F90:359
#2  0x56f1e9 in __hco_interface_gc_mod_MOD_hcoi_gc_final
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/GeosCore/hco_interface_gc_mod.F90:1240
#3  0x4d09ec in __emissions_mod_MOD_emissions_final
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/GeosCore/emissions_mod.F90:358
#4  0x43b265 in cleanup_
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/GeosCore/cleanup.F90:117
#5  0xd72412 in __error_mod_MOD_geos_chem_stop
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/GeosUtil/error_mod.F90:535
#6  0xd728c9 in __error_mod_MOD_error_stop
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/GeosUtil/error_mod.F90:446
#7  0x40661f in geos_chem
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/Interfaces/GCClassic/main.F90:489
#8  0x40ca8a in main
        at /home/-/gc_025x03125_geosfp_fullchem/CodeDir/src/GEOS-Chem/Interfaces/GCClassic/main.F90:32
Segmentation fault (core dumped)

What are the steps to reproduce the bug?

Running ./gclassic

Please attach any relevant configuration and log files.

No response

What GEOS-Chem version were you using?

14.4.2

What environment were you running GEOS-Chem on?

Local cluster

What compiler and version were you using?

gcc 10 2 0

Will you be addressing this bug yourself?

Yes

In what configuration were you running GEOS-Chem?

GCClassic

What simulation were you running?

Full chemistry

As what resolution were you running GEOS-Chem?

0.25x0.3125

What meterology fields did you use?

GEOS-FP

Additional information

No response

@Naaimaben Naaimaben added the category: Bug Something isn't working label Nov 25, 2024
@yantosca yantosca self-assigned this Nov 25, 2024
@yantosca yantosca added the topic: Runtime Error Related to runtime issues (e.g. simulation stopped w/ error) label Nov 25, 2024
@yantosca
Copy link
Contributor

Thanks for writing @Naaimaben. I think this means that you are running out of available memory on your system. Or you may have submitted the job to a queue that has a hard memory limit. You could try reducing the number of diagnostics that are turrned on to just the outputs that you want. That will reduce memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Bug Something isn't working topic: Runtime Error Related to runtime issues (e.g. simulation stopped w/ error)
Projects
None yet
Development

No branches or pull requests

2 participants