 |
 |
 |
|
|
|
[Sponsors] | ||||
Node 0: Process xxxx: Received signal SIGSEGV |
 |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
March 14, 2024, 01:40
|
It worked for me when I turn off continuous flow interaction
|
#41 |
|
New Member
karthikvatvat
Join Date: Dec 2014
Location: Bangalore
Posts: 7
Rep Power: 11  |
It worked for me when I turn off continuous flow interaction in DPM panel
|
|
|
|
|
|
March 14, 2024, 01:42
|
|
#42 | |
|
New Member
karthikvatvat
Join Date: Dec 2014
Location: Bangalore
Posts: 7
Rep Power: 11 |
Quote:
Yes , I have it fails to run even I turn off continuous phase interaction in DPM settings. |
||
|
|
|
||
|
March 18, 2024, 01:23
|
Solved this error for my case
|
#43 |
|
New Member
ankit
Join Date: Oct 2015
Posts: 2
Rep Power: 0 |
I was using C_T_RG in my UDF and was getting a similar error & fluent was exiting. Referred to UDF manual and entered
solve/set/expert in fluent panel and turned on Keep temporary solver memory from being freed? Yes This was perhaps happening because these gradient values were not being stored for access by UDF. Worked for me and fluent didn't got killed. But, after initialization, fluent exited again with same error. Any help on this???? Last edited by ankit_tiwari; March 18, 2024 at 03:11. Reason: Faced issues. |
|
|
|
|
|
|
| Tags |
| fluent, r15.0, upgrade |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Free Surface Ship Flow | timfranke | OpenFOAM Running, Solving & CFD | 322 | March 3, 2021 09:04 |
| mpirun, best parameters | pablodecastillo | Hardware | 18 | November 10, 2016 12:36 |
| The fluent stopped and errors with "Emergency: received SIGHUP signal" | yuyuxuan | FLUENT | 0 | December 3, 2013 22:56 |
| FLUENT received fatal signal (ACCESS_VIOLATION) | osamaghani | FLUENT | 2 | March 31, 2012 16:15 |
| 999999 (../../src/mpsystem.c@1123):mpt_read: failed:errno = 11 | UDS_rambler | FLUENT | 2 | November 22, 2011 09:46 |
11Likes
Linear Mode
