-
Notifications
You must be signed in to change notification settings - Fork 34
Segmentation fault (core dumped) and simulation stops executing #181
Hello together,
This is my first question in github, so I apologize if I am not following the usual guidelines for asking questions.
I want to simulate a directed energy deposition process and want to use the results for model order reduction for a scientific publication.
To become familiar with the program, I first wanted to simulate the hollow_cylinder example. I am interested in the evolving residual stress field, so I run the "master_app_mechanical.i" input file.
Command in the terminal:
~/moose_projects/malamute$ ./malamute-opt -i ./examples/directed_energy_deposition/hollow_cylinder/master_app_mechanical.i > logfile.log 2> logfile_err.log &
On two seperate hardware systems I get always after the 13th time step the following error error:
[1]+ Segmentation fault (core dumped) ./malamute-opt -i ./examples/...
Desktop-PC Information (Linux)
Model: Hewlett-Packard HP Z440 Workstation
Memory: 32.0 GiB
Processor: Intel Xeon E5-1630 v3 x 8
Graphics: AMD CAICOS
Disk Capacity: 512.1 GB (200GB free)
OS Name: Ubuntu 24.04.2 LTS
OS Type: 64-bit
Kernel Version: Linux 6.11.0-17-generic
Laptop-PC Information (WSL Subsystem for Windows)
Memory: 16 GiB
Processor: Intel Core i7-1370P
In my error file "logfile_err.log" there is no error.
If I run only the "sub_app_thermal.i" input file the simulation runs normal and the .e files have all been created.
Does anyone have any suggestions for solving the problem?
Thank you very much.
All reactions
Replies: 2 comments 4 replies
UPDATE: The following message comes from the gdb debugger after timestep 13
Assertion `find_side != find_elem->second.end()' failed
Material property does not have side entry
at /home/users/jku/moose_projects/malamute/moose/framework/build/header_symlinks/MaterialPropertyStorage.h, line 465
Stack frames: 16
0: libMesh::print_trace(std::ostream&)
1: /home/users/jku/moose_projects/malamute/moose/framework/libmoose-dbg.so.0(+0x2cac3e9) [0x7ffff61323e9]
2: MaterialPropertyStorage::prolongStatefulProps(unsigned int, std::vector<std::vector<QpMap, std::allocator >, std::allocator<std::vector<QpMap, std::allocator > > > const&, libMesh::QBase const&, libMesh::QBase const&, MaterialPropertyStorage&, unsigned int, libMesh::Elem const&, int, int, int)
3: ProjectMaterialProperties::onElement(libMesh::Elem const*)
4: ThreadedElementLoopBase<libMesh::StoredRange<__gnu_cxx::__normal_iterator<libMesh::Elem const**, std::vector<libMesh::Elem const*, std::allocator<libMesh::Elem const*> > >, libMesh::Elem const*> >::operator()(libMesh::StoredRange<__gnu_cxx::__normal_iterator<libMesh::Elem const**, std::vector<libMesh::Elem const*, std::allocator<libMesh::Elem const*> > >, libMesh::Elem const*> const&, bool)
5: /home/users/jku/moose_projects/malamute/moose/framework/libmoose-dbg.so.0(+0x1769d49) [0x7ffff4befd49]
6: FEProblemBase::meshChangedHelper(bool)
7: FEProblemBase::adaptMesh()
8: TransientBase::incrementStepOrReject()
9: TransientBase::execute()
10: MooseApp::executeExecutioner()
11: MooseApp::run()
12: /home/users/jku/moose_projects/malamute/malamute-dbg(+0x7d8c) [0x55555555bd8c]
13: main
14: __libc_start_main
15: /home/users/jku/moose_projects/malamute/malamute-dbg(+0x6079) [0x55555555a079]
[0] /home/users/jku/moose_projects/malamute/moose/framework/build/header_symlinks/MaterialPropertyStorage.h, line 465, compiled Mar 3 2025 at 10:48:50
Abort(1) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[Thread 0x7fffda632700 (LWP 57684) exited]
[Thread 0x7fffdae95700 (LWP 57683) exited]
[Inferior 1 (process 57676) exited with code 01]
All reactions
Hello @jannissimo - thank you for your question and for adding the extra debug output information.
I want to loop @dewenyushu in to this conversation, as she created this example, and might have a quick answer as to what is going on.
All reactions
Hi, I am facing the same problem and would appreciate any help. @dewenyushu have you had a chance to look into this issue? Thanks in advance!
All reactions
I'm also facing the exact same issue. The solver stops with the same error as mentioned by @jannissimo after 13th time step.
Could you please provide any update to this please. @cticenhour @dewenyushu
All reactions
This problem seems to be caused by moose, due to the stateful material projection when using adaptive mesh refinement at the moving boundaries. See idaholab/moose#30274. If anyone solves this problem, please let me know. Many thanks! @cticenhour @jannissimo @dewenyushu @whitmanjack