CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > ANSYS Meshing & Geometry

[ICEM] "segmentation violation" error

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

Reply
 
LinkBack Thread Tools Display Modes
Old   March 25, 2009, 14:56
Default "segmentation violation" error
  #1
Member
 
^_^
Join Date: Mar 2009
Posts: 36
Rep Power: 8
Jasmine is on a distinguished road
Hi,

Got this error meassage "segmentation violation" many times. For example, when I tried to generate a find grid in ICEM CFD by chaning the maximum element size from 30 to 24. or even when I check a coarse grid quanlity, the error meassage show up!
I actually just added 2GB memory which is not the same brand as the old 2G meomry. Will that be a problem?

What might be the reason?And how should I deal with it? Thanks in advance.

Last edited by Jasmine; March 25, 2009 at 15:30.
Jasmine is offline   Reply With Quote

Old   March 25, 2009, 23:49
Default
  #2
New Member
 
Join Date: Mar 2009
Location: Hyderabad
Posts: 6
Rep Power: 8
fauka is on a distinguished road
Hi!!

Most of the cases of "segmentation violation" error are because of memory problems. You can check it with the task manager if there is any such problem. Other than that, I think you need to work on your geometry for holes or any such defects.
fauka is offline   Reply With Quote

Old   March 26, 2009, 17:29
Default
  #3
Member
 
^_^
Join Date: Mar 2009
Posts: 36
Rep Power: 8
Jasmine is on a distinguished road
Thanks!
Well, I changed 2 new memory which is the same brand as my old one, and it works. That kind of error message does not show up so far.
Jasmine is offline   Reply With Quote

Old   October 29, 2009, 05:49
Default
  #4
New Member
 
hashem
Join Date: May 2009
Posts: 17
Rep Power: 8
hashem_1064 is on a distinguished road
yes, this error is strongly related to the lack of memory.
hashem_1064 is offline   Reply With Quote

Old   October 29, 2009, 08:03
Default
  #5
Super Moderator
 
Ryne Whitehill
Join Date: Aug 2009
Posts: 313
Rep Power: 10
rwryne is on a distinguished road
Quote:
Originally Posted by hashem_1064 View Post
yes, this error is strongly related to the lack of memory.
I do not think that is the sole case. A coworker and I were getting this message often with ICEM 11. We would basically have to restart the project fresh from the CAD geometry when it would happen. Would use exact same parameters (aka exact same memory usage) and it would work sometimes, others not.

Have not seen this message at all since switching to ICEM 12.
rwryne is offline   Reply With Quote

Old   November 11, 2009, 23:00
Default Clear the memory.
  #6
Senior Member
 
PSYMN's Avatar
 
Simon Pereira
Join Date: Mar 2009
Location: Ann Arbor, MI
Posts: 2,662
Blog Entries: 1
Rep Power: 36
PSYMN has a spectacular aura aboutPSYMN has a spectacular aura about
Hey Ryne,

It may have been that some processes were still running, or at least still hogging memory. For instance, during the tetra process, elements are swapped around or removed. The matrix keeps the memory slots for these cells for a while and may have an issue clearing the memory in some situations. Other times, a process like Prism.exe may continue to run and be hogging memory even after you think it is done.

The undo buffer may also hog a lot of memory, for instance, if you did a global mesh edit operation operation like converting linear tets to quadratic (or tet to hex), your memory would hold both the old and new tets so that you could "undo" the operation.

Many of these processes, and UNDO its self, were significantly improved at 12.0, which gave us memory improvements, etc. Actually, add mid-side nodes still needs this fix , but at least you can clear the undo buffer easily now.

When you were quitting and restarting 11.0, you were clearing your memory in a rough but effective way.

I am attaching an image of the memory improvements for Octree Tetra at 12.1 (due out later this month).
Attached Images
File Type: gif Opti_02.gif (74.9 KB, 77 views)
File Type: gif Opti_01.gif (93.1 KB, 69 views)
PSYMN is offline   Reply With Quote

Old   November 12, 2009, 09:12
Default
  #7
Super Moderator
 
Ryne Whitehill
Join Date: Aug 2009
Posts: 313
Rep Power: 10
rwryne is on a distinguished road
Quote:
Originally Posted by PSYMN View Post
Hey Ryne,

It may have been that some processes were still running, or at least still hogging memory. For instance, during the tetra process, elements are swapped around or removed. The matrix keeps the memory slots for these cells for a while and may have an issue clearing the memory in some situations. Other times, a process like Prism.exe may continue to run and be hogging memory even after you think it is done.

The undo buffer may also hog a lot of memory, for instance, if you did a global mesh edit operation operation like converting linear tets to quadratic (or tet to hex), your memory would hold both the old and new tets so that you could "undo" the operation.

Many of these processes, and UNDO its self, were significantly improved at 12.0, which gave us memory improvements, etc. Actually, add mid-side nodes still needs this fix , but at least you can clear the undo buffer easily now.

When you were quitting and restarting 11.0, you were clearing your memory in a rough but effective way.

I am attaching an image of the memory improvements for Octree Tetra at 12.1 (due out later this month).
I am excited for 12.1 then!

v12.0 has been great, haven't gotten the segmentation violation error with it. However, I am getting a large memory spike on the "disconnecting orphan cells" step of mesh generation. This often crashes ICEM with no warning (i.e. the process just disappears). I submitted a help ticket to the techsupport who confirmed this spike, and they recommended using batch mode until v12.1 comes out to avoid this. This seems to be working, but I often forget to check the box

Thanks for the reply,

Ryne
rwryne is offline   Reply With Quote

Old   December 20, 2013, 18:06
Default
  #8
Senior Member
 
ali
Join Date: Oct 2009
Posts: 157
Rep Power: 7
alinik is on a distinguished road
I am getting this error in cfx-solve. Any idea how I can resolve this issue?
I have increased the memory allocation factor upto 10 and still getting the same error. I am running CFX remotely on a linux based supercomputer.

Thanks
alinik is offline   Reply With Quote

Old   January 16, 2015, 06:00
Default how to allocate memory for segemental violation error
  #9
New Member
 
vishwanath
Join Date: Jan 2015
Posts: 1
Rep Power: 0
vishwanath is on a distinguished road
hi every one,

I am finding error as segemental error. how to resolve it? ...
can you explain the steps to avoid it.
vishwanath 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
Compile problem ivanyao OpenFOAM Running, Solving & CFD 1 October 12, 2012 09:31
Problem with compile the setParabolicInlet ivanyao OpenFOAM Running, Solving & CFD 6 September 5, 2008 20:50
Compiling problems with hello worldC fw407 OpenFOAM Installation 21 January 6, 2008 18:38
DecomposePar links against liblamso0 with OpenMPI jens_klostermann OpenFOAM Bugs 11 June 28, 2007 17:51
user subroutine error CFDUSER CFX 2 December 9, 2006 07:31


All times are GMT -4. The time now is 09:13.