Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Taro

New member
Dear all,I was trying to run a simulation. I am getting error:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x7FE34E0F76D7
#1 0x7FE34E0F7D1E
#2 0x7FE34D5F327F
#3 0x1E63E37 in taugb3.6165 at module_ra_rrtmg_lw.f90:?
#4 0x1E860C9 in __rrtmg_lw_taumol_MOD_taumol
#5 0x1E9DF66 in __rrtmg_lw_rad_MOD_rrtmg_lw
#6 0x1EB2212 in __module_ra_rrtmg_lw_MOD_rrtmg_lwrad
#7 0x18A6B4D in __module_radiation_driver_MOD_radiation_driver
#8 0x1998107 in __module_first_rk_step_part1_MOD_first_rk_step_part1
#9 0x131B12F in solve_em_
#10 0x11AAB65 in solve_interface_
#11 0x4787D2 in __module_integrate_MOD_integrate
#12 0x407FA3 in __module_wrf_top_MOD_wrf_run
and i found the PBLH in wrfout is 0,I choose rttmg for ra_sw_physics.I was not able to resolve this problem. Here's my file.
 

Attachments

  • New Folder.zip
    55.1 KB · Views: 13
Hello Taro,

Sorry to hear you ran into a seg fault. One thing I would suggest doing is going into the Frequently Asked Questions and look under What is the most common reason for a segmentation fault. I've run into similar issues before, and it could be due to a number of reasons. One fix I had was to unlimit the stack size of my computer (ulimit -s unlimited). If you're running on a cloud environment or you don't have privilege to modify the stack size, then I would contact your admin. You can also try some different physics schemes, however I've run a very similar scheme and I didn't run into any issues. If you're still running into issues, I would increase your debug level to 50 or 100 as that might help describe what's going on and where it's crashing. I hope that helped.

Thanks,
JeremyB
 
@Taro
In your rsl* files, you have numerous CFL errors, which means the model is becoming unstable. This is likely due to the fact that your time_step is larger than 6xDX. However, you are using a resolution of 75, which is incredibly high-resolution. What is the resolution of your input data?
 
Top