CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM

interDyMFoam crashes with Segmentation Fault

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   December 12, 2010, 19:26
Default interDyMFoam crashes with Segmentation Fault
  #1
Member
 
Join Date: Mar 2009
Location: Sydney, New South Wales, Australia
Posts: 42
Rep Power: 8
rassilon is on a distinguished road
I am trying to use the dynamic meshing solver interDyMFoam, to run a case, however the solver crashes at the beginning of the run with the following error:

Quote:
Only call if constructed with history capability#0 Foam::error:rintStack(Foam::Ostream&) in "/usr/OpenFoam/OpenFOAM-1.6/lib/linux64GccDPOpt/libOpenFOAM.so"
#1 Foam::error::abort() in "/usr/OpenFoam/OpenFOAM-1.6/lib/linux64GccDPOpt/libOpenFOAM.so"
#2 Foam::hexRef8::getSplitPoints() const in "/usr/OpenFoam/OpenFOAM-1.6/lib/linux64GccDPOpt/libdynamicMesh.so"
#3 Foam::dynamicRefineFvMesh::selectUnrefinePoints(do uble, Foam::PackedList<1u> const&, Foam::Field<double> const&) const in "/usr/OpenFoam/OpenFOAM-1.6/lib/linux64GccDPOpt/libdynamicFvMesh.so"
#4 Foam::dynamicRefineFvMesh::update() in "/usr/OpenFoam/OpenFOAM-1.6/lib/linux64GccDPOpt/libdynamicFvMesh.so"
#5 main in "/usr/OpenFoam/OpenFOAM-1.6/applications/bin/linux64GccDPOpt/interDyMFoam"
#6 __libc_start_main in "/lib/libc.so.6"
#7 _start at /usr/src/packages/BUILD/glibc-2.9/csu/../sysdeps/x86_64/elf/start.S:116


From function hexRef8::getSplitPoints()
in file polyTopoChange/polyTopoChange/hexRef8.C at line 4873.

FOAM aborting
I created the mesh using snappyHexMesh, and checkMesh identifies no errors, however the solver runs perfectly well with the same mesh created in Gambit and converted using fluentToFoam.

Is this a problem with the solver or with the meshing utility? I have not had any problems with snappy before now. I have also tried running the case using interFoam, which seems to work OK, so I think it may be a problem with either the interDyMFoam solver, or a combination of this solver and the meshing utility.

Has anybody else experienced this, and/or have any suggestions that may help me overcome this?

Thanks in advance,


R
rassilon is offline   Reply With Quote

Old   December 12, 2010, 19:48
Default
  #2
Super Moderator
 
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 8,488
Blog Entries: 34
Rep Power: 86
wyldckat is just really nicewyldckat is just really nicewyldckat is just really nicewyldckat is just really nice
Greetings Rassilon,

OpenFOAM 1.6? OpenFOAM is already in version 1.7.x! The latest stable release is 1.7.1! There are so many things that have been fixed since 1.6... you better consider upgrading your OpenFOAM installation.
Better yet, you can keep your current 1.6 and add the latest 1.7.1 and/ot 1.7.x version to your tool belt! Check this post for more information on how to have more than one OpenFOAM version: OpenFoam Installation in Redhat Enterprise linux 5 post #17

Now, if your case still crashes with 1.7.1 or even 1.7.x, then it's most probably a serious bug! On the other hand, it might be a very simple issue: one of the boundary patches of your mesh has zero faces attributed to it. Therefore, no related points were found. Er, I reiterate, it seems to be in the moving part of the mesh... My best bet would be to upgrade

Best regards and good luck!
Bruno
wyldckat is offline   Reply With Quote

Old   December 12, 2010, 20:31
Default
  #3
Member
 
Join Date: Mar 2009
Location: Sydney, New South Wales, Australia
Posts: 42
Rep Power: 8
rassilon is on a distinguished road
Quote:
Originally Posted by wyldckat View Post
Greetings Rassilon,

OpenFOAM 1.6? OpenFOAM is already in version 1.7.x! The latest stable release is 1.7.1! There are so many things that have been fixed since 1.6... you better consider upgrading your OpenFOAM installation.
Better yet, you can keep your current 1.6 and add the latest 1.7.1 and/ot 1.7.x version to your tool belt! Check this post for more information on how to have more than one OpenFOAM version: OpenFoam Installation in Redhat Enterprise linux 5 post #17

Now, if your case still crashes with 1.7.1 or even 1.7.x, then it's most probably a serious bug! On the other hand, it might be a very simple issue: one of the boundary patches of your mesh has zero faces attributed to it. Therefore, no related points were found. Er, I reiterate, it seems to be in the moving part of the mesh... My best bet would be to upgrade

Best regards and good luck!
Bruno
Hi Bruno,

Thanks for the response. yes, I am still running 1.6, though I have tried it on a 1.7 installation, and I still get the same problem.

Cheers,


R
rassilon is offline   Reply With Quote

Old   December 29, 2010, 16:23
Default
  #4
Member
 
Dave
Join Date: Jul 2010
Posts: 97
Rep Power: 7
daveatstyacht is on a distinguished road
I had the same error come up in 1.7.1 when I tried to use both dynamic remeshing and dynamic mesh motion (I wanted a mesh that would remesh when it got too distorted from the motion). I am not sure what is causing the problem, but in my case it would run until it got to the first remesh and then it would fail with that error message. I had chalked it up to the effect of mesh motion, but I guess it may be something more to do with the remeshing process itself.
daveatstyacht is offline   Reply With Quote

Old   January 5, 2011, 18:31
Default
  #5
Member
 
Join Date: Mar 2009
Location: Sydney, New South Wales, Australia
Posts: 42
Rep Power: 8
rassilon is on a distinguished road
Quote:
Originally Posted by daveatstyacht View Post
I had the same error come up in 1.7.1 when I tried to use both dynamic remeshing and dynamic mesh motion (I wanted a mesh that would remesh when it got too distorted from the motion). I am not sure what is causing the problem, but in my case it would run until it got to the first remesh and then it would fail with that error message. I had chalked it up to the effect of mesh motion, but I guess it may be something more to do with the remeshing process itself.

Hmmm. In my case, it definitely seems to be something to do with the mesh that is produced in snappyHexMesh. Using the same mesh that is imported from Fluent allows interDyMFoam to run as it should.

It's a real pain, as it makes the advantages of the snappyHexMesh utility pretty much worthless, as we are going to have to mesh by hand in Gambit now.

It's also pretty disappointing that this is an error that has survived through two new versions of the code. I hope that it gets cleaned up for the next release.


R
rassilon is offline   Reply With Quote

Old   January 5, 2011, 20:22
Default
  #6
Super Moderator
 
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 8,488
Blog Entries: 34
Rep Power: 86
wyldckat is just really nicewyldckat is just really nicewyldckat is just really nicewyldckat is just really nice
Greetings to all!

If the issue isn't reported to the bug section in www.openfoam.com/bugs then it's less likely that it will ever get fixed!

By the way, have you considered trying the Project-Extend's OpenFOAM 1.6-ext? I only know that it has more and other features than the official version has, so you might want to give it a try!

Best regards,
Bruno
wyldckat is offline   Reply With Quote

Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Segmentation fault when running dieselFoam or dieselEngineFoam in parallel francesco OpenFOAM Bugs 3 June 10, 2011 09:30
forrtl: severe (174): SIGSEGV, segmentation fault occurred therockyy FLOW-3D 7 January 19, 2011 23:52
ParaView segmentation fault only for multiphase gwierink OpenFOAM 9 March 25, 2010 08:23
segmentation fault usker CD-adapco 5 March 6, 2007 00:14
KIVA and Segmentation Fault Felix Main CFD Forum 2 January 18, 2006 02:24


All times are GMT -4. The time now is 02:48.