Some versions of MFiX had an issue where backtraces were not being printed when the solver hit a problem at runtime, leading to these unexplained “Process exit” messages. Was there anything in the console, or the
I ran your case on my machine, using the most recent version of the code.
After a few warnings, it produced this error:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7f9192e55c02 in ???
#1 0x7f9192e54e45 in ???
#2 0x7f91df9c5b7f in ???
#3 0x7f9193306064 in __set_ic_dem_mod_MOD_set_ic_dem
#4 0x7f91932dc5cc in __make_arrays_des_mod_MOD_make_arrays_des
#5 0x7f91931b39ba in __main_MOD_initialize
#6 0x7f919334849e in run_mfix_
#7 0x7f91931b3c42 in __main_MOD_run_mfix0
#8 0x7f91931a6206 in f2py_rout_mfixsolver_main_run_mfix0
so something is going wrong with the simulation. We are looking into it. If it’s an MFiX bug we will try to include a fix in the upcoming 20.2 release.